Mailman 3 November 2012 - docs

[issue10796] readline completion flaw
by Éric Araujo Nov. 3, 2012

Nov. 3, 2012

Éric Araujo added the comment: I think I get it: Python sets custom delimiters that include '-' because for the Python REPL, it’s not possible to have one identifier with a dash, so it’s considered a delimiter and when you press tab, a new completion is started. For a custom REPL however, you may want to have dashes as legal parts of your completed words, so you want to call set_completer_delims. Reclassifying as a doc patch. ---------- assignee: -> docs@python components: +Documentation -Library (Lib) keywords: +easy nosy: +docs@python stage: -> needs patch versions: +Python 2.7, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10796> _______________________________________

1 0

[issue16394] Improving tee() memory footprint
by Serhiy Storchaka Nov. 3, 2012

Nov. 3, 2012

Changes by Serhiy Storchaka <storchaka(a)gmail.com>: ---------- nosy: -serhiy.storchaka stage: -> needs patch type: performance -> enhancement versions: -Python 2.6, Python 3.1 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16394> _______________________________________

1 0

[issue15125] argparse: positional arguments containing - in name not handled well
by Simon Law Nov. 3, 2012

Nov. 3, 2012

Simon Law added the comment: 15125-2.patch applies to the default branch. It makes dest behave the same for positional and optional arguments in terms of name mangling. Also, there is a backward-compatibility path in Namespace to support old-style getattr() access. However, it's not documented as we really don't want people to use it. ---------- Added file: http://bugs.python.org/file27863/15125-2.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15125> _______________________________________

1 0

[issue16394] Improving tee() memory footprint
by Carsten Milkau Nov. 3, 2012

Nov. 3, 2012

Changes by Carsten Milkau <chat.noir(a)arcor.de>: ---------- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16394> _______________________________________

1 0

[issue15125] argparse: positional arguments containing - in name not handled well
by Simon Law Nov. 3, 2012

Nov. 3, 2012

Simon Law added the comment: Note that 15125-1.patch applies to Python 2.7 cleanly as it is a bugfix. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15125> _______________________________________

1 0

[issue15125] argparse: positional arguments containing - in name not handled well
by Éric Araujo Nov. 3, 2012

Nov. 3, 2012

Changes by Éric Araujo <merwok(a)netwok.org>: Removed file: http://bugs.python.org/file27859/15125-1.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15125> _______________________________________

1 0

[issue15125] argparse: positional arguments containing - in name not handled well
by Simon Law Nov. 3, 2012

Nov. 3, 2012

Simon Law added the comment: Sorry, there was a small typo in the previous patch. Here's the newer version. ---------- Added file: http://bugs.python.org/file27860/15125-1.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15125> _______________________________________

1 0

[issue15125] argparse: positional arguments containing - in name not handled well
by Simon Law Nov. 3, 2012

Nov. 3, 2012

Simon Law added the comment: >> But patching the module to allow explicitly setting dest via keyword >> argument shouldn't hurt anybody. > > I agree that it wouldn't hurt anybody. If you can find a way to do > this, feel free to provide a patch. > > However, the correct way to have one name for the attribute (i.e. > dest=) and one name for the help (i.e. metavar=) is to use the > metavar argument like so: > > parser.add_argument('positional_args', metavar='positional-args') I don't think that making ``dest`` more magical is a good idea. In the included patch, you'll find a change that makes the ValueError tell people about ``metavar``, which is the right way to go about things anyway. > That said, this is not the first time I've seen someone run into this > problem. I think the documentation could be improved in a few ways: > > (1) In the "name or flags" section, describe how the flags (for > optional arguments) are translated into both a default "dest" > (stripping initial '-' and converting '-' to '_') and into a default > "metavar" (stripping initial '-' and uppercasing). Part of this is > in the "dest" and "metavar" documentation, but probably belongs up > in the "name or flags" documentation. Add cross-references to "dest" > and "metavar" sections. In the included patch. > (2) In the "name or flags" section, describe how the name (for > positional arguments) are translated into the same default "dest" > and "metavar" (no string munging at all). Again, move stuff from the > "dest" and "metavar" sections as necessary. Add cross-references to > "dest" and "metavar" sections. > > (3) In the "dest" section and somewhere in the "parse_args" section, > describe how "getattr" can be used to get attributes whose names > aren't valid Python identifiers. Maybe cross-reference this section > from the edits in (2). If we make optional and positional arguments consistent, and provide backwards-compatibility for positional arguments, then these two are not necesssary. ---------- nosy: +sfllaw Added file: http://bugs.python.org/file27859/15125-1.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15125> _______________________________________

1 0

[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.
by Serhiy Storchaka Nov. 3, 2012

Nov. 3, 2012

Serhiy Storchaka added the comment: PySequence_Tuple() was changed to PySequence_List() in the changeset 4714aff4bf75 in 2004. Are there any measurements which show PySequence_List() faster than PySequence_Tuple() on modern Python? I don't see any references in 4714aff4bf75 description. ---------- nosy: +serhiy.storchaka _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16395> _______________________________________

1 0

[issue16395] Documentation claims that PySequence_Fast returns a tuple, when it actually returns a list.
by Éric Araujo Nov. 3, 2012

Nov. 3, 2012

Éric Araujo added the comment: Larry, any objection to backporting this? ---------- assignee: -> docs@python components: +Documentation -Interpreter Core nosy: +docs@python, eric.araujo, larry stage: -> patch review versions: -Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16395> _______________________________________

1 0