Mailman 3 July 2010 - docs

Small Typo
by Ted Gibbons July 7, 2010

July 7, 2010

Hello, I noticed a small typo in your otherwise wonderful documentation. In the explanation for the -c option in the section explaining the command line interface options<http://docs.python.org/using/cmdline.html#interface-options>, the second sentence starts with "*command* can be one ore more statements..." I assume that "ore" is supposed to be "or". Have a good day and keep up the good work! -- Ted Gibbons University of Maryland Graduate Research Assistant

2 1

Docs are not printable
by Bruce Korb July 7, 2010

July 7, 2010

The bug is that I need to burn trees for small pieces of the docs and it is not possible with firefox to print the useful text with that left side menu stuff. Please put it on the right side and all will be well. Thank you. http://docs.python.org/library/xml.dom.minidom.html

4 6

[issue9182] document “--” as a way to distinguish option w/ narg='+' from positional argument in argparse
by Sergey Konoplev July 6, 2010

July 6, 2010

Sergey Konoplev <gray.ru(a)gmail.com> added the comment: Thank you for the hint. It is realy not so obvious. May be it is worth to add "--" into the usage string this way usage: [-h] [-b BAR [BAR ...]] -- foo Otherwise it leads to misunderstanding. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9182> _______________________________________

1 0

[issue9182] document “--” as a way to distinguish option w/ narg='+' from positional argument in argparse
by Éric Araujo July 6, 2010

July 6, 2010

Éric Araujo <merwok(a)netwok.org> added the comment: I always forget that not all programs follow getopt-style parsing rules, thanks for the reminder. ---------- keywords: +easy resolution: -> accepted title: argparse: optional argument w/ narg='+' conflicts w/ positional argsument -> document “--” as a way to distinguish option w/ narg='+' from positional argument in argparse _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9182> _______________________________________

1 0

[issue9182] argparse: optional argument w/ narg='+' conflicts w/ positional argsument
by Éric Araujo July 6, 2010

July 6, 2010

Éric Araujo <merwok(a)netwok.org> added the comment: I was suggesting a doc bug only if the current doc didn’t advertise clearly this way of combining nargs with positional arguments. Using “--” is most certainly standard and right, Using “--” to explicitly signal positional arguments is most certainly right and standard, but people have to read about that for the first time somewhere. In a perfect world, that would be in their shell’s man page, but better add a word about it in the reference. The “--” marker is actually mentioned in one section: http://docs.python.org/dev/library/argparse#arguments-containing I’m reopening, suggesting that a line be added to explain the standard “--” separator for use cases like Sergey’s. ---------- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python resolution: invalid -> stage: -> needs patch status: closed -> open _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9182> _______________________________________

2 1

[issue9182] argparse: optional argument w/ narg='+' conflicts w/ positional argsument
by Éric Araujo July 6, 2010

July 6, 2010

Éric Araujo <merwok(a)netwok.org> added the comment: Duh, please ignore the first two lines, I forgot to remove them after rephrasing my comment. Sorry. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9182> _______________________________________

1 0

[issue9158] PyArg_ParseTuple y* documentation is incorrect
by Terrence Cole July 6, 2010

July 6, 2010

New submission from Terrence Cole <terrence(a)zettabytestorage.com>: The documented C type for y* should be [Py_buffer], not [Py_buffer *], as with the documentation for z* and the convention followed by the other types. I'm not sure what 'type' this issue should have. I've set it at 'crash' initially, since that's how the bug manifested for me. ---------- assignee: docs@python components: Documentation files: PyArgs_ParseTuple_ystar_doc_fix.patch keywords: patch messages: 109285 nosy: docs@python, terrence priority: normal severity: normal status: open title: PyArg_ParseTuple y* documentation is incorrect type: crash versions: Python 3.2 Added file: http://bugs.python.org/file17862/PyArgs_ParseTuple_ystar_doc_fix.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9158> _______________________________________

3 5

[issue9166] minor misstatement in What's New in 2.7
by Daniel Stutzbach July 5, 2010

July 5, 2010

New submission from Daniel Stutzbach <daniel(a)stutzbachenterprises.com>: "Finally, the Mapping abstract base class now raises a NotImplemented exception..." should read "returns" instead of "raises" Here's the relevant code patch: http://svn.python.org/view/python/trunk/Lib/_abcoll.py?r1=78800&r2=81414&pa… ---------- assignee: docs@python components: Documentation keywords: patch messages: 109327 nosy: docs@python, stutzbach priority: normal severity: normal stage: patch review status: open title: minor misstatement in What's New in 2.7 versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9166> _______________________________________

2 1

[issue9160] Documentation link of 3.2 not working at docs.python.org
by Eli Bendersky July 5, 2010

July 5, 2010

New submission from Eli Bendersky <eliben(a)gmail.com>: This link: http://docs.python.org/dev/py3k/ Isn't working. I have always used it to see the latest documentation from 3.2, and it is linked in the left-hand side of the screen on docs.python.org as "Python 3.2 (in development)" under "Docs for other versions" if you're, for example here: http://docs.python.org/py3k/ ---------- assignee: docs@python components: Documentation messages: 109289 nosy: docs@python, eliben priority: normal severity: normal status: open title: Documentation link of 3.2 not working at docs.python.org versions: Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9160> _______________________________________

4 4

[issue8472] itertools.filterfalse() function missing
by Georg Brandl July 4, 2010

July 4, 2010

Georg Brandl <georg(a)python.org> added the comment: Thanks, applied the suggestion in r82548. ---------- status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8472> _______________________________________

1 0