Mailman 3 February 2014 - docs

bug report index method
by sdfjsfjaei-thomas＠yahoo.de Feb. 15, 2014

Feb. 15, 2014

Hello, can you please file a bug report about this inconsistency: for list None is not allowed in the index method, while for str it is. Also there are 2 different formats for optional paremeters in the help. >>> ''.index('', 0, None) 97: 0 >>> [].index('', 0, None) Traceback (most recent call last): File "<pyshell#169>", line 1, in <module> [].index('', 0, None) TypeError: slice indices must be integers or None or have an __index__ method >>> help(''.index) Help on built-in function index: index(...) S.index(sub[, start[, end]]) -> int Like S.find() but raise ValueError when the substring is not found. >>> help([].index) Help on built-in function index: index(...) L.index(value, [start, [stop]]) -> integer -- return first index of value. Raises ValueError if the value is not present.

1 0

[issue20626] Manager documentation unclear about lists and thread safeness
by Berker Peksag Feb. 14, 2014

Feb. 14, 2014

Changes by Berker Peksag <berker.peksag(a)gmail.com>: ---------- nosy: +sbt _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20626> _______________________________________

1 0

[issue20573] "built-in repr()" function link on the repr module documentation is incorrect
by Roundup Robot Feb. 14, 2014

Feb. 14, 2014

Roundup Robot added the comment: New changeset 7c47529bda0e by Benjamin Peterson in branch '2.7': fix links to builtin repr function (closes #20573) http://hg.python.org/cpython/rev/7c47529bda0e ---------- nosy: +python-dev resolution: -> fixed stage: -> committed/rejected status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20573> _______________________________________

1 0

[issue20573] "built-in repr()" function link on the repr module documentation is incorrect
by Éric Araujo Feb. 14, 2014

Feb. 14, 2014

Changes by Éric Araujo <merwok(a)netwok.org>: ---------- nosy: +eric.araujo _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20573> _______________________________________

1 0

[issue20626] Manager documentation unclear about lists and thread safeness
by Zachary Ware Feb. 14, 2014

Feb. 14, 2014

Changes by Zachary Ware <zachary.ware(a)gmail.com>: ---------- stage: -> needs patch type: -> enhancement versions: -Python 3.1, Python 3.2, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20626> _______________________________________

1 0

[issue20626] Manager documentation unclear about lists and thread safeness
by Irvin Probst Feb. 14, 2014

Feb. 14, 2014

Changes by Irvin Probst <probst(a)gmail.com>: ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20626> _______________________________________

1 0

[issue10728] argparse.ArgumentParser.print_help uses sys.stdout
by Jan-Philip Gehrcke Feb. 14, 2014

Feb. 14, 2014

Jan-Philip Gehrcke added the comment: The version action currently writes to stderr. The _VersionAction(Action)'s __call__() method finishes off with parser.exit(message=formatter.format_help()) and parser.exit() by default writes to stderr. Here, Steven says "Help is definitely intended to print to stdout." and I expected the same to happen regarding the version information. Why should it go to stderr? I see that this is a minor problem and only if someone here agrees I would open an issue for that. ---------- nosy: +jgehrcke _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10728> _______________________________________

1 0

[issue9694] argparse required arguments displayed under "optional arguments"
by paul j3 Feb. 14, 2014

Feb. 14, 2014

Changes by paul j3 <ajipanca(a)gmail.com>: Added file: http://bugs.python.org/file34074/alt_grouping2.py _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9694> _______________________________________

1 0

[issue9694] argparse required arguments displayed under "optional arguments"
by paul j3 Feb. 14, 2014

Feb. 14, 2014

paul j3 added the comment: Here's another possible solution: add a `help_groups` parameter to ArgumentParser. It is a list of base argument group names. `parser.add_argument(...)' places the action in one of those groups. This is a generalization of the current code which creates two groups titled 'positional arguments' and 'optional arguments', and assigns actions based on 'optional strings' (e.g. '-f','--foo'). 'help_groups' could have 1, 2, or 3 items. 1 - just one argument group 2 - the current postional/optional split, but with user chosen names 3 - a 'positional', 'required', and 'optional' split. A 4 way split that distinguishes splits positionals between those that allow 0 values and 1 or more, is possible, but probably not that useful. The changes are in the ArgumentParser.__init__ and _add_action methods. 'subparsers' do not inherit this parameter. I have not explored how it plays out with 'parents'. 'test_argparse.py' runs fine. ---------- keywords: +patch Added file: http://bugs.python.org/file34073/helpgroups.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9694> _______________________________________

1 0

[issue19680] Help missing for exec and print
by Bohuslav "Slavek" Kabrda Feb. 14, 2014

Feb. 14, 2014

New submission from Bohuslav "Slavek" Kabrda: Steps to reproduce: [bkabrda@zizalka python]$ python >>> help() help> keywords <snip> # prints lots of keywords including "print" and "exec" </snip> help> print no documentation found for 'print' So either keywords should not list "print" and "exec" or the documentation for them should be built. IIUC, the help for these should be part of pydoc_data/topics.py, which gets generated by Doc/tools/sphinxext/pyspecific.py. However, in revision [1] some topics got removed ("print" and "exec" amongst them) without the commit message saying anything helpful. Either way, this is inconsistent and should be fixed (assuming that Python 2.7 is still supposed to get this sort of fixes). Thanks. [1] http://hg.python.org/cpython/rev/76aa98f69251 ---------- assignee: docs@python components: Documentation messages: 203625 nosy: bkabrda, docs@python priority: normal severity: normal status: open title: Help missing for exec and print versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19680> _______________________________________

4 5