Mailman 3 January 2014 - docs

[issue20252] Argument Clinic howto: small typo in y# translation
by Ryan Smith-Roberts Jan. 19, 2014

Jan. 19, 2014

New submission from Ryan Smith-Roberts: type -> types ---------- assignee: docs@python components: Documentation files: argument_clinic_howto_y-hash.patch keywords: patch messages: 208076 nosy: docs@python, larry, rmsr priority: normal severity: normal status: open title: Argument Clinic howto: small typo in y# translation type: enhancement versions: Python 3.4 Added file: http://bugs.python.org/file33458/argument_clinic_howto_y-hash.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20252> _______________________________________

2 3

py2exe in Python3.3 documentation
by Damir Hakimov Jan. 18, 2014

Jan. 18, 2014

Hello all! Is it correct to place py2exe in Python3.3 documentation? http://docs.python.org/3.3/using/windows.html#py2exe Does py2exe support Python3.3?

2 4

[issue17814] Popen.stdin/stdout/stderr documentation should mention object type
by Nikolaus Rath Jan. 18, 2014

Jan. 18, 2014

New submission from Nikolaus Rath: The subprocess documentation currently just says that Popen.stdin et all are "file objects", which is linked to the glossary entry. This isn't very helpful, as it doesn't tell whether the streams are bytes or text streams. Suggested patch: diff --git a/Doc/library/subprocess.rst b/Doc/library/subprocess.rst --- a/Doc/library/subprocess.rst +++ b/Doc/library/subprocess.rst @@ -677,21 +677,29 @@ .. attribute:: Popen.stdin - If the *stdin* argument was :data:`PIPE`, this attribute is a :term:`file - object` that provides input to the child process. Otherwise, it is ``None``. + If the *stdin* argument was :data:`PIPE`, this attribute is a + :class:`io.BufferedWriter` (if the *universal_newlines* argument + was False) or :class:`io.TextIOWrapper` (if the + *universal_newlines* argument was True) object that provides input + to the child process. Otherwise, it is ``None``. .. attribute:: Popen.stdout - If the *stdout* argument was :data:`PIPE`, this attribute is a :term:`file - object` that provides output from the child process. Otherwise, it is ``None``. + If the *stdout* argument was :data:`PIPE`, this attribute is a + :class:`io.BufferedReader` (if the *universal_newlines* argument + was False) or :class:`io.TextIOWrapper` (if the + *universal_newlines* argument was True) object that provides output + from the child process. Otherwise, it is ``None``. .. attribute:: Popen.stderr - If the *stderr* argument was :data:`PIPE`, this attribute is a :term:`file - object` that provides error output from the child process. Otherwise, it is - ``None``. + If the *stderr* argument was :data:`PIPE`, this attribute is a + :class:`io.BufferedReader` (if the *universal_newlines* argument + was False) or :class:`io.TextIOWrapper` (if the + *universal_newlines* argument was True) object that provides output + from the child process. Otherwise, it is ``None``. .. attribute:: Popen.pid ---------- assignee: docs@python components: Documentation messages: 187535 nosy: Nikratio, docs@python priority: normal severity: normal status: open title: Popen.stdin/stdout/stderr documentation should mention object type type: enhancement _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17814> _______________________________________

6 10

[issue20135] FAQ need list mutation answers
by R. David Murray Jan. 17, 2014

Jan. 17, 2014

R. David Murray added the comment: I *thought* there was a FAQ entry for that. Didn't think to look for it in the design section though :(. Nor is the title likely to catch the eye of someone wondering why their default argument modifications are being unexpectedly persistent. Also, the fact that it starts out with the sentence "This type of bug commonly bites neophyte programmers" is, IMO, a clue it should be in the programming section. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20135> _______________________________________

1 0

[issue20135] FAQ need list mutation answers
by Ezio Melotti Jan. 17, 2014

Jan. 17, 2014

Ezio Melotti added the comment: http://docs.python.org/3/faq/design.html#why-are-default-values-shared-betw… ---------- nosy: +ezio.melotti _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20135> _______________________________________

1 0

[issue20135] FAQ need list mutation answers
by Fran Bull Jan. 17, 2014

Jan. 17, 2014

Changes by Fran Bull <fran.bull(a)gmail.com>: ---------- keywords: +patch Added file: http://bugs.python.org/file33502/20135.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20135> _______________________________________

1 0

[issue20135] FAQ need list mutation answers
by Fran Bull Jan. 16, 2014

Jan. 16, 2014

Fran Bull added the comment: Perhaps a 3rd FAQ something like this?: Why is changing a list in one instance of a class also changing it in another instance of the same class? This happens: >>> class A(object): ... def __init__(self, fruit=[]): ... self.fruit = fruit ... >>> an_A = A() >>> an_A.fruit.append('apple') >>> another_A = A() >>> print another_A.fruit ['apple'] >>> another_A.fruit.append('banana') >>> print another_A.fruit ['apple', 'banana'] >>> print an_A.fruit ['apple', 'banana'] >>> print an_A.fruit is another_A.fruit True >>> print an_A.fruit is A().fruit True because of a combination of the above two FAQs, first the default argument is evaluated when the 'def' statement is executed and creates an instance of list. After that new instances of A have a variable 'fruit' that is the name for that instance of list. I'm not sure whether I should be using as general terms as possible for the Q, i.e. 'mutable object' instead of 'list'. I'll reread http://docs.python.org/devguide/documenting.html and the FAQs before writing the patch. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20135> _______________________________________

1 0

[issue20281] time.strftime %z format specifier is the same as %Z
by R. David Murray Jan. 16, 2014

Jan. 16, 2014

R. David Murray added the comment: Ah, you are correct. I'm not sure what page I was looking at before. Maybe I hadn't switched away from the python2 page. ---------- versions: +Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20281> _______________________________________

1 0

[issue20281] time.strftime %z format specifier is the same as %Z
by Mike Owens Jan. 16, 2014

Jan. 16, 2014

Mike Owens added the comment: I'm looking right at the 3.3 docs right now. %z is in the table. 8.1.8. strftime() and strptime() Behavior ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20281> _______________________________________

1 0

[issue20281] time.strftime %z format specifier is the same as %Z
by R. David Murray Jan. 16, 2014

Jan. 16, 2014

R. David Murray added the comment: The %z table entry exists only in the 3.4 (dev) docs, not the 3.3 docs. There is no doc change needed for 3.3, since it doesn't mention %z except in the footnote. And yes, I should have mentioned that the datetime versions only work with aware timezones. You can get an aware local time from email.utils.localtime(). (This localtime function may eventually move to the datetime module if it can be made more reliable, but it works fine for the use cases the email package needs.) ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20281> _______________________________________

1 0