Mailman 3 July 2012 - docs

[issue9708] cElementTree iterparse does not support "parser" argument
by Florent Xicluna 21 Jul '12

21 Jul '12

Florent Xicluna <florent.xicluna(a)gmail.com> added the comment: Either the documentation or the implementation should be fixed in 3.3, because they do not match. ---------- nosy: +eli.bendersky versions: +Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9708> _______________________________________

1 0

[issue15063] Source code links for JSON documentation
by Bryce Verdier 21 Jul '12

21 Jul '12

New submission from Bryce Verdier <bryceverdier(a)gmail.com>: In some parts of the documentation there are links to the source code. While looking in the JSON documentation that link isn't there. Not sure if this is wanted or if it's complete. But I'm submitting it anyway in the hopes of feedback. ---------- assignee: docs@python components: Documentation files: json_source_link.patch keywords: patch messages: 162750 nosy: docs@python, louiscipher priority: normal severity: normal status: open title: Source code links for JSON documentation type: enhancement versions: Python 3.3 Added file: http://bugs.python.org/file26006/json_source_link.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15063> _______________________________________

4 4

[issue15399] processName key is un-/mis-documented in 2.6 and up
by Gunnlaugur Thor Briem 20 Jul '12

20 Jul '12

New submission from Gunnlaugur Thor Briem <gunnlaugur(a)gmail.com>: The ``processName`` format mapping key in logging formats works in versions 2.6.*, 2.7.* and 3.1.* onwards; in 2.5 and down and in 3.0.1, ``format`` fails when this key is present in the format. But in 2.6.8 docs, this mapping key is not documented: http://docs.python.org/release/2.6.8/library/logging.html http://docs.python.org/release/3.0.1/library/logging.html and in 2.7.3 and 3.1.5 and 3.2.3 docs, it is documented but there is no note that it is new in any particular version (unlike ``funcName``, for which there is “Changed in version 2.5: funcName was added”): http://docs.python.org/release/2.7.3/library/logging.html http://docs.python.org/release/3.1.5/library/logging.html http://docs.python.org/release/3.2.3/library/logging.html Consistent with (what I think are the) version note conventions, these seem like the actions to take: - In 2.6 docs, add processName, and insert the note “Changed in version 2.6: processName was added” - In 2.7 docs, insert that same note - In docs for 3.1 and up, insert the note “Changed in version 3.1: processName was added” ---------- assignee: docs@python components: Documentation messages: 165852 nosy: docs@python, gthb priority: normal severity: normal status: open title: processName key is un-/mis-documented in 2.6 and up type: enhancement versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15399> _______________________________________

3 2

[issue14201] Documented caching for shared library's __getattr__ and __getitem__ is incorrect
by Meador Inge 19 Jul '12

19 Jul '12

Meador Inge <meadori(a)gmail.com> added the comment: The general wording and example look good; thanks. I reworded things a little. Updated patch attached. ---------- stage: needs patch -> commit review Added file: http://bugs.python.org/file26443/issue14201-v2.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14201> _______________________________________

1 0

[issue9254] __import__ docstring should recommend importlib.import_module()
by Roundup Robot 18 Jul '12

18 Jul '12

Roundup Robot <devnull(a)psf.upfronthosting.co.za> added the comment: New changeset 751f28564a45 by R David Murray in branch '2.7': Closes #9254: backport __import__ docstring/doc mentions of importlib. http://hg.python.org/cpython/rev/751f28564a45 ---------- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9254> _______________________________________

1 0

[issue14332] Better explain "junk" concept in difflib doc
by Eli Bendersky 16 Jul '12

16 Jul '12

Eli Bendersky <eliben(a)gmail.com> added the comment: I agree. Any improvement is preferred over just letting this decay in the issue tracker ;-) ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14332> _______________________________________

1 0

[issue15375] Trivial for fix in the subprocess documentation
by Renato Cunha 16 Jul '12

16 Jul '12

New submission from Renato Cunha <renato(a)renatocunha.com>: The word "child" is needlessly repeated in the subprocess documentation. This trivial patch fixes this. ---------- assignee: docs@python components: Documentation files: subprocess.diff keywords: patch messages: 165670 nosy: docs@python, trovao priority: normal severity: normal status: open title: Trivial for fix in the subprocess documentation type: enhancement versions: Python 2.7 Added file: http://bugs.python.org/file26408/subprocess.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15375> _______________________________________

3 2

[issue14201] Documented caching for shared library's __getattr__ and __getitem__ is incorrect
by Erik Johansson 16 Jul '12

16 Jul '12

Erik Johansson <erik(a)ejohansson.se> added the comment: Document the difference between __getattr__ and __getitem__. ---------- keywords: +patch Added file: http://bugs.python.org/file26402/issue14201.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14201> _______________________________________

1 0

[issue14787] pkgutil.walk_packages returns extra modules
by Chris Jerdonek 16 Jul '12

16 Jul '12

Chris Jerdonek <chris.jerdonek(a)gmail.com> added the comment: > This isn't an easy one to fix - you basically need something along the lines of a PEP 406 style import engine API in order to do the import without having potentially adverse effects on the state in the sys module. By adverse, do you just mean side effects? If so, since the documentation doesn't explicitly say so, is there any reason for the user to think there shouldn't be side effects? For example, I tried this in Python 2.7: >>> import os, sys, pkgutil, unittest >>> len(sys.modules) 86 >>> g = pkgutil.walk_packages([os.path.dirname(unittest.__file__)]) >>> len(sys.modules) 86 >>> for i in g: ... pass ... >>> len(sys.modules) 95 Or maybe this isn't what you mean. If not, can you provide an example? ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14787> _______________________________________

1 0

[issue14787] pkgutil.walk_packages returns extra modules
by Nick Coghlan 16 Jul '12

16 Jul '12

Nick Coghlan <ncoghlan(a)gmail.com> added the comment: I just realised this is going to behave strangely with namespace packages as well: the __import__ step will pick up *every* portion of the namespace package, not just those defined in the identified subset of sys.path. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14787> _______________________________________

1 0