Mailman 3 February 2014 - docs

Re: [docs] Add doc examples for DictReader and DictWriter (issue 20351)
by vadmium+py＠gmail.com 10 Feb '14

10 Feb '14

http://bugs.python.org/review/20351/diff/10699/Doc/library/csv.rst File Doc/library/csv.rst (right): http://bugs.python.org/review/20351/diff/10699/Doc/library/csv.rst#newcode1… Doc/library/csv.rst:166: Wonderful SPAM I think the space argument to print() shouldn’t be there; print() should already be adding the single space separator on its own. Also, making the capitalisation agree with the DictWriter example below would be nice. http://bugs.python.org/review/20351/

1 0

[issue9694] argparse required arguments displayed under "optional arguments"
by Martin Panter 10 Feb '14

10 Feb '14

Martin Panter added the comment: A new “required arguments” section seems too arbitrary to me. It would clash with the “positional arguments” heading, since those are also required by default. I would go with the heading “options”, as a noun. That term seems to be well used, at least on Linux and Wikipedia (see https://en.wikipedia.org/wiki/Command-line_option). Other terms are “flag” and “switch”. In this thread I see two arguments against this: 1. Eric Smith prefers to retain the noun “arguments”. How about something like “non-positional arguments” then? 2. Steven Bethard is worried about backwards compatibility. I thought the Python people were happy to make these sort of changes each minor release (e.g. 3.4 to 3.5). The module’s source code uses the term “optionals” a lot more than this one heading. It would be clearer if this term were dropped, or only used for things that are truly optional. So even if you can’t fix the help output until Python 4, please fix the documentation and the rest of the source code :) ---------- nosy: +vadmium _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9694> _______________________________________

1 0

[issue19871] json module won't parse a float that starts with a decimal point
by Ezio Melotti 10 Feb '14

10 Feb '14

Ezio Melotti added the comment: I missed this comment from Serhiy: > There are too many cases where json and Python syntax differ. How many differences there are between the two? I think we might add notes to the table at http://docs.python.org/3/library/json.html#encoders-and-decoders (either something similar to the notes in the table at http://docs.python.org/3/library/stdtypes.html#mutable-sequence-types, or just a couple of lines in a third column). If there are too many differences and we follow the specs we can just add a note saying that the decoding is done according to the specs, add a link to them, and mention a few examples that are valid in Python but not in JSON (like Serhiy did in his message). ---------- keywords: +easy nosy: +terry.reedy _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19871> _______________________________________

1 0

[issue19906] Typo in urllib documentation
by Claudiu.Popa 10 Feb '14

10 Feb '14

New submission from Claudiu.Popa: In the first note from urllib.rst, there is a reference to urllib being replaced by urllib2 in Python 3, which is False. ---------- assignee: docs@python components: Documentation files: urllib2.patch keywords: patch messages: 205359 nosy: Claudiu.Popa, docs@python priority: normal severity: normal status: open title: Typo in urllib documentation type: enhancement versions: Python 2.7 Added file: http://bugs.python.org/file33002/urllib2.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19906> _______________________________________

4 5

[issue20573] "built-in repr()" function link on the repr module documentation is incorrect
by Ned Deily 09 Feb '14

09 Feb '14

Changes by Ned Deily <nad(a)acm.org>: ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20573> _______________________________________

1 0

[issue19363] Python 2.7's future_builtins.map is not compatible with Python 3's map
by Nick Coghlan 08 Feb '14

08 Feb '14

Nick Coghlan added the comment: Switched to be a docs-only bug as Gareth suggested. ---------- assignee: rhettinger -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python, ncoghlan resolution: wont fix -> stage: committed/rejected -> needs patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19363> _______________________________________

1 0

[issue20477] Add examples of using the new contentmanager api to the email docs
by R. David Murray 07 Feb '14

07 Feb '14

New submission from R. David Murray: Here are the examples I promised to write in issue 18891. ---------- assignee: docs@python components: Documentation, email files: contentmanager-examples.patch keywords: patch messages: 209922 nosy: barry, docs@python, r.david.murray priority: normal severity: normal stage: commit review status: open title: Add examples of using the new contentmanager api to the email docs type: behavior versions: Python 3.4 Added file: http://bugs.python.org/file33850/contentmanager-examples.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20477> _______________________________________

2 2

[issue20386] socket.SocketType enum overwrites import of _socket.SocketType
by Ethan Furman 06 Feb '14

06 Feb '14

Ethan Furman added the comment: Thanks for the hints, Georg! ---------- Added file: http://bugs.python.org/file33945/issue20386.stoneleaf.04.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20386> _______________________________________

1 0

[issue12691] tokenize.untokenize is broken
by Gareth Rees 06 Feb '14

06 Feb '14

Gareth Rees added the comment: I did some research on the cause of this issue. The assertion was added in this change by Jeremy Hylton in August 2006: <https://mail.python.org/pipermail/python-checkins/2006-August/055812.html> (The corresponding Mercurial commit is here: <http://hg.python.org/cpython/rev/cc992d75d5b3#l217.25>). At that point I believe the assertion was reasonable. I think it would have been triggered by backslash-continued lines, but otherwise it worked. But in this change <http://hg.python.org/cpython/rev/51e24512e305> in March 2008 Trent Nelson applied this patch by Michael Foord <http://bugs.python.org/file9741/tokenize_patch.diff> to implement PEP 263 and fix issue719888. The patch added ENCODING tokens to the output of tokenize.tokenize(). The ENCODING token is always generated with row number 0, while the first actual token is generated with row number 1. So now every token stream from tokenize.tokenize() sets off the assertion. The lack of a test case for tokenize.untokenize() in "full" mode meant that it was (and is) all too easy for someone to accidentally break it like this. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12691> _______________________________________

1 0

[issue20488] importlib title and introduction are out of date
by R. David Murray 06 Feb '14

06 Feb '14

New submission from R. David Murray: Now that importlib *is* the import system in CPython, the title ("An Implementation of import") and the intro ("a reference implementation that is easier to comprehend than..." seem to me like they are out of date and should be reworded. ---------- assignee: docs@python components: Documentation messages: 209994 nosy: brett.cannon, docs@python, eric.snow, r.david.murray priority: normal severity: normal status: open title: importlib title and introduction are out of date type: behavior versions: Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20488> _______________________________________

3 3