Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +4841
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue32321>
___
_
Change by Srinivas Reddy T :
--
pull_requests: +4843
___
Python tracker
<https://bugs.python.org/issue15852>
___
___
Python-bugs-list mailing list
Unsubscribe:
Srinivas Reddy T added the comment:
dtdev@dtdev-centos $ python3
Python 3.6.3 (default, Oct 11 2017, 18:17:01)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-18)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> impo
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +4883
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue32360>
___
_
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +4886
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue32418>
___
_
Change by Srinivas Reddy T :
--
pull_requests: +4889
___
Python tracker
<https://bugs.python.org/issue32360>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +4893
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue32413>
___
_
Srinivas Reddy T added the comment:
Done. exec(...)'s documentation covers raymond's comment.
--
nosy: +thatiparthy
___
Python tracker
<https://bugs.python.o
Change by Srinivas Reddy T :
--
pull_requests: +4894
___
Python tracker
<https://bugs.python.org/issue32384>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Srinivas Reddy T :
--
pull_requests: +4902
___
Python tracker
<https://bugs.python.org/issue32360>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Srinivas Reddy T :
--
pull_requests: +4903
___
Python tracker
<https://bugs.python.org/issue32338>
___
___
Python-bugs-list mailing list
Unsubscribe:
Srinivas Reddy T added the comment:
Renaming the method `copy()` to `__copy__` breaks the API. I would rather have
an alias for `__copy__`.
I agree that it is not documented, but some users tend to assume public methods
are documented and use them.
So i think it is better to not to break
New submission from Srinivas Reddy T :
I ran these queries on cpython repo.
➜ cpython git:(master) ✗ grep -r . -e return --include=\*.py | grep
NotImplemented | wc -l
196
➜ cpython git:(master) ✗ grep -r . -e raise --include=\*.py | grep
NotImplemented | wc -l
295
I have always used
New submission from Srinivas Reddy T :
https://github.com/python/cpython/pull/7116
--
messages: 320018
nosy: thatiparthy
priority: normal
severity: normal
status: open
title: remove unecessary variable assignments
type: resource usage
versions: Python 3.7, Python 3.8
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +7417
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue33908>
___
_
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +7418
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +7421
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +7437
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue33894>
___
_
Srinivas Reddy T added the comment:
Hi Raymond,
I find your statement hard to understand.I agree with Solstag, it is
always helpful to have an example.
+1 for solstag wording.
--
nosy: +thatiparthy
___
Python tracker
<ht
New submission from Srinivas Reddy T :
I think it is better to use "Big-O notation" than a generic wording "computer
science notation". I understand the use of latter, but i guess it helps the
programmer since it makes him/her to google it or ask some one if he/she
Change by Srinivas Reddy T :
--
title: use correct term than generic wording -> use standard term than generic
wording
___
Python tracker
<https://bugs.python.org/issu
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +7535
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Srinivas Reddy T :
--
pull_requests: +9238
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issue20216>
___
___
Py
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +9240
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +9245
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue24653>
___
_
Change by Srinivas Reddy T :
--
keywords: +patch
pull_requests: +9273
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue33947>
___
_
New submission from Srinivas Reddy T:
Added descriptive message to assert statement in datetime module.
Since _check_date_fields does the job of data integrity, i did not check for
ValueError, TypeError checks in the function.
However, i am not sure of the adding descriptive messages to the
New submission from Srinivas Reddy T:
Updated to barry's new email address.
--
components: Tests
files: barry_email.patch
keywords: patch
messages: 202714
nosy: thatiparthy
priority: normal
severity: normal
status: open
title: Changing barry's email to ba...@python.or
Srinivas Reddy T added the comment:
The exact behavior is present in 2.7 version too. So tagging 2.7 to 3.4
--
nosy: +thatiparthy
versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3
___
Python tracker
<http://bugs.python.org/issue20
29 matches
Mail list logo