Mailman 3 November 2010 - docs

[issue8340] bytearray undocumented on trunk
by Antoine Pitrou 20 Nov '10

20 Nov '10

Antoine Pitrou <pitrou(a)free.fr> added the comment: Done in r86602. ---------- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8340> _______________________________________

1 0

[issue8890] Use tempfile instead of /tmp in examples
by Mauro Navarro Baraldi 20 Nov '10

20 Nov '10

Mauro Navarro Baraldi <mauro.baraldi(a)gmail.com> added the comment: Replace to most use of /tmp/tempfile for just tempfile, as sugested before. ---------- keywords: +patch nosy: +maurobaraldi Added file: http://bugs.python.org/file19698/py3k-docs.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8890> _______________________________________

1 0

[issue10461] Use with statement throughout the docs
by Éric Araujo 20 Nov '10

20 Nov '10

New submission from Éric Araujo <merwok(a)netwok.org>: The docs contain numerous examples that would trigger resource warnings under 3.2 (for example “open(...).read()”). They should be changed to use (and thus promote) the with statement. Not adding the “easy” keyword, since grepping for those things is not easy. Not sure we’ll backport that to 3.1 and 2.7. ---------- assignee: docs@python components: Documentation messages: 121545 nosy: docs@python, eric.araujo priority: normal severity: normal stage: needs patch status: open title: Use with statement throughout the docs versions: Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10461> _______________________________________

10 45

[issue9182] document “--” as a way to distinguish option w/ narg='+' from positional argument in argparse
by Daniel Albeseder 20 Nov '10

20 Nov '10

Daniel Albeseder <kotan(a)gmx.at> added the comment: I did the patch for adding the "--" in the generated usage text inside issue 9338. ---------- nosy: +Kotan _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9182> _______________________________________

1 0

[issue5066] IDLE documentation for Unix obsolete/incorrect
by Éric Araujo 20 Nov '10

20 Nov '10

Changes by Éric Araujo <merwok(a)netwok.org>: ---------- assignee: -> docs@python nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue5066> _______________________________________

1 0

Documentation error: 2.2.2. Executable Python Scripts
by Fabrizio Marana 20 Nov '10

20 Nov '10

Dear Sir/Madam, *Bug: *In section 2.2.2. on page http://docs.python.org/py3k/tutorial/interpreter.html you mention "On Windows systems, there is no notion of an “executable mode” ".** This is wrong. Since Windows NT4 and onwards, there is a notion of a "path extension", which is similar to the Unix executable mode, but invoked differently. *Solution:* 1. Using the GUI: a. Right-click on "My computer" b. go to "properties" c. go to "environment variables" (dependent on the OS: NT 4.0, W2K, XP, Vista, W7) d. add the string ";PY" to the end of the existing string OR 2. Using the Command line (temporary for that command interpreter only until it is exited) At the CLI (cmd.exe; commnd.com) ">" type: SET PATHEXT=%PATHEXT%;.PY Python executables can now be executed on a command line without specifically invoking the Python interpreter as the Python installer automatically associates .py files with python.exe. (Which is a prerequisite) *Example:* C:\Program Files\Python\Tools\Scripts>SET PATHEXT=%PATHEXT%;.PY C:\Program Files\Python\Tools\Scripts>2to3.py At least one file or directory argument required. Use --help to show usage. HTH, Fabrizio Marana

1 0

[issue10439] PyCodec C API is not documented in reST
by Alexander Belopolsky 20 Nov '10

20 Nov '10

New submission from Alexander Belopolsky <belopolsky(a)users.sourceforge.net>: Python Codec Registry and support functions are well documented in codecs.h header file. It should be easy to convert that to reST. ---------- assignee: docs@python components: Documentation keywords: easy messages: 121329 nosy: belopolsky, docs@python, haypo, lemburg, loewis priority: normal severity: normal stage: needs patch status: open title: PyCodec C API is not documented in reST versions: Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10439> _______________________________________

5 11

[issue10351] Add autocompletion for keys in dictionaries
by Éric Araujo 20 Nov '10

20 Nov '10

Éric Araujo <merwok(a)netwok.org> added the comment: I will review your patch later today. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10351> _______________________________________

1 0

[issue10463] Wrong return value for xml.etree.ElementTree.parse()
by Daniel Seither 20 Nov '10

20 Nov '10

New submission from Daniel Seither <post(a)tiwoc.de>: Cite from http://docs.python.org/library/xml.etree.elementtree.html > xml.etree.ElementTree.parse(source, parser=None) > > Parses an XML section into an element tree. source is a filename or > file object containing XML data. parser is an optional parser > instance. If not given, the standard XMLParser parser is used. > Returns an ElementTree instance. The last sentence should be "Returns an Element instance." I verified this error for the Python versions as listed in this issue. In 2.5, the information was imprecise but correct. ---------- assignee: docs@python components: Documentation messages: 121571 nosy: docs@python, tiwoc priority: normal severity: normal status: open title: Wrong return value for xml.etree.ElementTree.parse() versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10463> _______________________________________

2 3

[issue10396] stdin argument to pdb.Pdb doesn't work unless you also set Pdb.use_rawinput = False
by Éric Araujo 19 Nov '10

19 Nov '10

Éric Araujo <merwok(a)netwok.org> added the comment: This is a sound argument. I had also missed your comment “Note that the pdb docs direct you the cmd docs, which clearly document the need to set use_rawinput, so this is not even a doc bug”, which I was about to write with other words :) There was actually no need to reopen this bug. ---------- assignee: docs@python -> components: +Library (Lib) -Documentation resolution: -> duplicate stage: patch review -> committed/rejected status: open -> closed superseder: -> cmd.py always uses raw_input, even when another stdin is specified _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10396> _______________________________________

1 0