Mailman 3 July 2013 - docs

[issue18389] document that os.path.relpath does not interrogate the file system
by R. David Murray 12 Jul '13

12 Jul '13

R. David Murray added the comment: Thanks, Madison. I tweaked the wording slightly, but the essence is the same :). ---------- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18389> _______________________________________

1 0

[issue18389] document that os.path.relpath does not interrogate the file system
by Roundup Robot 12 Jul '13

12 Jul '13

Roundup Robot added the comment: New changeset 70837970c5d8 by R David Murray in branch '3.3': #18389: Clarify that relpath does not access the file system. http://hg.python.org/cpython/rev/70837970c5d8 New changeset 7de05609e390 by R David Murray in branch 'default': #18389: Clarify that relpath does not access the file system. http://hg.python.org/cpython/rev/7de05609e390 New changeset 1345d8dbcb19 by R David Murray in branch '2.7': #18389: Clarify that relpath does not access the file system. http://hg.python.org/cpython/rev/1345d8dbcb19 ---------- nosy: +python-dev _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18389> _______________________________________

1 0

[issue18433] Clarify venv docs about which methods check for pre-existing paths
by Brett Cannon 12 Jul '13

12 Jul '13

New submission from Brett Cannon: E.g. setup_python and create_directories both check that the paths they will create pre-exist, but the docs don't mention this. ---------- assignee: docs@python components: Documentation messages: 192938 nosy: brett.cannon, carljm, docs@python priority: normal severity: normal status: open title: Clarify venv docs about which methods check for pre-existing paths versions: Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18433> _______________________________________

3 4

[issue18434] Update venv example to use setuptools
by Brett Cannon 12 Jul '13

12 Jul '13

New submission from Brett Cannon: Now that Distribute is just a shell for setuptools 0.8, the example in the venv docs for installing pip and setuptools in a venv should be updated to use setuptools (in case anyone uses that code as a script themselves). ---------- assignee: docs@python components: Documentation messages: 192939 nosy: brett.cannon, carljm, docs@python priority: normal severity: normal status: open title: Update venv example to use setuptools versions: Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18434> _______________________________________

2 3

[issue17987] test.support.captured_stderr, captured_stdin not documented
by Fred L. Drake, Jr. 11 Jul '13

11 Jul '13

New submission from Fred L. Drake, Jr.: The captured_stderr and captured_stdin context managers aren't documented, and should be. ---------- assignee: docs@python components: Documentation keywords: easy messages: 189311 nosy: docs@python, fdrake priority: normal severity: normal stage: needs patch status: open title: test.support.captured_stderr, captured_stdin not documented type: enhancement versions: Python 3.3, Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17987> _______________________________________

6 20

[issue18044] Email headers do not properly decode to unicode.
by Tim Rawlinson 11 Jul '13

11 Jul '13

New submission from Tim Rawlinson: In Python 3.3 decoding of headers to unicode is supposed to be automatic but fails in several cases, including one shown as successful in the documentation: >>> msg = message_from_string('Subject: =?utf-8?q?=C3=89ric?=\n\n', policy=default) >>> msg['Subject'] '=?utf-8?q?=C3=89ric?=' >>> msg = message_from_string('To: =?utf-8?q?=C3=89ric <foo(a)example.com>\n\n', policy=default) >>> msg['To'] '=?utf-8?q?=C3=89ric?= <foo(a)example.com>' Although the following works: >>> msg = message_from_string('Subject: =?utf-8?q?Eric?=\n\n', policy=default) >>> msg['Subject'] 'Eric' Though this does not: >>> msg = message_from_string('To: =?utf-8?q?Eric?= <foo(a)example.com>\n\n', policy=default) >>> msg['To'] '=?utf-8?q?Eric?= <foo(a)example.com>' And just to prove some things are working as they should: >>> msg = message_from_string("Subject: =?gb2312?b?1eLKx9bQzsSy4srUo6E=?=\n\n", policy=default) >>> msg['Subject'] '这是中文测试！' ---------- assignee: docs@python components: Documentation, email messages: 189862 nosy: Tim.Rawlinson, barry, docs@python, r.david.murray priority: normal severity: normal status: open title: Email headers do not properly decode to unicode. type: behavior versions: Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18044> _______________________________________

4 4

[issue18389] document that os.path.relpath does not interrogate the file system
by Madison May 11 Jul '13

11 Jul '13

Madison May added the comment: Patch for 3.4 added. I tried to keep things short and sweet. ---------- Added file: http://bugs.python.org/file30892/Issue18389_3-4.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18389> _______________________________________

1 0

[issue11908] Weird `slice.stop or sys.maxint`
by Ram Rachum 11 Jul '13

11 Jul '13

New submission from Ram Rachum <cool-rr(a)cool-rr.com>: In the documentation for `itertools.islice` I see this line: it = iter(xrange(s.start or 0, s.stop or sys.maxint, s.step or 1)) Is it really okay to do `s.stop or sys.maxint`? I'm assuming this was targeting `None`, but what if `s.stop == 0`? And `s.step` could (pathologically) be `0` too, no? ---------- assignee: docs@python components: Documentation messages: 134276 nosy: cool-RR, docs@python priority: normal severity: normal status: open title: Weird `slice.stop or sys.maxint` type: behavior versions: Python 2.5, 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/issue11908> _______________________________________

8 13

[issue18424] sum() does not return only the sum of a sequence of numbers + PEP8 reccomandation
by Marco Buttu 10 Jul '13

10 Jul '13

New submission from Marco Buttu: The documentaion of sum(): Returns the sum of a sequence of numbers (NOT strings) plus the value of parameter 'start' (which defaults to 0). When the sequence is empty, returns start. A. According to the PEP-8 it should be: "Return the sum...", and "When the sequence is empty, return start.", like the other docs. For instance: >>> print(len.__doc__) len(object) -> integer Return the number of items of a sequence or mapping. B. When the second argument is a tuple or a list, you can add sequences of sequences: >>> sum([['a', 'b', 'c'], [4]], []) ['a', 'b', 'c', 4] >>> sum(((1, 2, 3), (1,)), (1,)) (1, 1, 2, 3, 1) C. sum() takes not just sequences: >>> sum({1: 'one', 2: 'two'}) 3 Maybe it is not a good idea to give a complete description of sum() in the docstring, but perhaps something "good enough". In any case, I think the lack of the PEP-8 recommendation should be fixed. ---------- assignee: docs@python components: Documentation messages: 192805 nosy: docs@python, marco.buttu priority: normal severity: normal status: open title: sum() does not return only the sum of a sequence of numbers + PEP8 reccomandation versions: Python 2.7, Python 3.1, Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18424> _______________________________________

5 10

[issue12731] python lib re uses obsolete sense of \w in full violation of UTS#18 RL1.2a
by Terry J. Reedy 10 Jul '13

10 Jul '13

Changes by Terry J. Reedy <tjreedy(a)udel.edu>: ---------- versions: +Python 3.4 -Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12731> _______________________________________

1 0