Mailman 3 August 2014 - docs

[issue22243] Documentation on try statement incorrectly implies target of except clause can be any assignable expression
by Michael Williamson Aug. 23, 2014

Aug. 23, 2014

New submission from Michael Williamson: In the docs for the try statement [1], part of the grammar is: try1_stmt ::= "try" ":" suite ("except" [expression ["as" target]] ":" suite)+ ["else" ":" suite] ["finally" ":" suite] The `target` rule allows any assignable expression (identifier, attributes, etc.). However, CPython appears to only allow identifiers as a target. The abstract grammar in the ast module [2] appears to confirm this. [1] https://docs.python.org/3.4/reference/compound_stmts.html#the-try-statement [2] https://docs.python.org/3.4/library/ast.html#abstract-grammar ---------- assignee: docs@python components: Documentation messages: 225611 nosy: docs@python, mwilliamson priority: normal severity: normal status: open title: Documentation on try statement incorrectly implies target of except clause can be any assignable expression versions: Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22243> _______________________________________

5 11

[issue22232] str.splitlines splitting on non-\r\n characters
by Terry J. Reedy Aug. 23, 2014

Aug. 23, 2014

Terry J. Reedy added the comment: Glossary fixed. I changed the components to Documention as you will handle email elsewhere. For library references: The key sentence currently used in all entries is "This method uses the universal newlines approach to splitting lines.", where *universal newlines* is linked to the glossary. 2.x has one entry for str and unicode. I propose to add "Unicode.splitlines also splits on '\x0b' ('\v'), '\x0c' ('\f'), '\x1c', '\x1d', '\x1e', '\x85', '\u2028', and '\u2029'." 3.x bytes entry is good as is. 3.x str entry is wrong. Replace with "This method splits on universal newlines and also on '\x0b' ('\v'), '\x0c' ('\f'), '\x1c', '\x1d', '\x1e', '\x85', '\u2028', and '\u2029'." The docstrings now contain about the same as the docs, minus the key line above. " Return a list of the lines in S, breaking at line boundaries. Line breaks are not included in the resulting list unless keepends is given and true." Between the sentences, I propose to add: "Boundaries are indicated by 'universal newlines' ('\x0a' ('\n'), '\x0d' ('\r'), and '\x0d\x0a' ('\r\n'))." for bytes, with the addition of "and '\x0b' ('\v'), '\x0c' ('\f'), '\x1c', '\x1d', '\x1e', '\x85', '\u2028', and '\u2029'" for unicode. ---------- assignee: -> docs@python components: +Documentation -Library (Lib), Unicode, email nosy: +docs@python stage: -> needs patch versions: +Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22232> _______________________________________

1 0

[issue15125] argparse: positional arguments containing - in name not handled well
by Keith Hughitt Aug. 23, 2014

Aug. 23, 2014

Keith Hughitt added the comment: Although it would be nice if the behavior were normalized between positional and optional args, it seems like doc patch would be the most straight-forward at this point. The down-side is that I suspect many people will assume the behavior for optional args, have it fail, and then consults the docs to see what happened. I would suggest making the note pretty obvious or early on in the docs for argparse. ---------- _______________________________________ 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 paul j3 Aug. 22, 2014

Aug. 22, 2014

paul j3 added the comment: It still needs a documentation patch. And if the documentation was clearer, would sfllaw's patch still be needed? ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15125> _______________________________________

1 0

flags is not a parameter in open
by Gert Aug. 20, 2014

Aug. 20, 2014

https://docs.python.org/3.0/library/os.html. says this: The following constants are options for the /flags/ parameter to the open() <https://docs.python.org/3.0/library/functions.html#open> function. ... os.O_NDELAY When I follow the link to the open function it does NOT have a flags parameter: open(/file/[, /mode='r'/[, /buffering=None/[, /encoding=None/[, /errors=None/[, /newline=None/[, /closefd=True/]]]]]])¶ <https://docs.python.org/3.0/library/functions.html#open> I am trying to solve this: My C-code uses: fd = open("/dev/ttyAMA0",O_RDW|O_NDELAY) the equivalent code in python3 (Raspberry-Pi) gives an error: fd = open("/dev/ttyAMA0",os.O_RDW|os.O_NDELAY) open() second argument must be str, not int -- Gert

2 2

[issue15125] argparse: positional arguments containing - in name not handled well
by Keith Hughitt Aug. 19, 2014

Aug. 19, 2014

Keith Hughitt added the comment: Any progress on this issue? Still persists in Python 3.4.1. ---------- nosy: +khughitt _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15125> _______________________________________

1 0

[issue7951] Should str.format allow negative indexes when used for __getitem__ access?
by Mark Lawrence Aug. 18, 2014

Aug. 18, 2014

Mark Lawrence added the comment: msg216038 suggests three options for the doc patch, does anybody have any preference or a better alternative? ---------- nosy: +BreamoreBoy _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue7951> _______________________________________

1 0

doc bug: PyUnicode_FromStringAndSize missing New Reference return tag in Py3
by Nick Aug. 14, 2014

Aug. 14, 2014

Problem for bytes and unicode doc for functions returning new objects examples are PyUnicode_FromStringAndSize and PyBytes_FromStringAndSize they are missing the Return value: New reference. beneath them, I think. -Nick

1 0

[issue22199] Embedding Python documentation error
by Jim Carroll Aug. 14, 2014

Aug. 14, 2014

New submission from Jim Carroll: On the page https://docs.python.org/2/extending/embedding.html#compiling-and-linking-un… The documentation makes the following reference: "...(use sysconfig.get_makefile_filename() to find its location)..." But this is incorrect. sysconfig was modified in 3.x (Issue 9877) to use this new name. In 2.x, the function has an underscore prefix: sysconfig._get_makefile_filename() ---------- assignee: docs@python components: Documentation messages: 225307 nosy: docs@python, jamercee priority: normal severity: normal status: open title: Embedding Python documentation error versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22199> _______________________________________

1 0

Minor PDF doc typo?
by Barry Davenport Aug. 14, 2014

Aug. 14, 2014

1 0