Mailman 3 September 2011 - docs

[issue12943] tokenize: add python -m tokenize support back
by Meador Inge Sept. 17, 2011

Sept. 17, 2011

Meador Inge <meadori(a)gmail.com> added the comment: > Did you get commit rights already? I have not. I still need to submit a contributor agreement as well. I plan to fax that today. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12943> _______________________________________

1 0

[issue12943] tokenize: add python -m tokenize support back
by Georg Brandl Sept. 17, 2011

Sept. 17, 2011

Georg Brandl <georg(a)python.org> added the comment: Looks good to me. Did you get commit rights already? ---------- nosy: +georg.brandl _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12943> _______________________________________

1 0

[issue12943] tokenize: add python -m tokenize support back
by Meador Inge Sept. 17, 2011

Sept. 17, 2011

Meador Inge <meadori(a)gmail.com> added the comment: v2 patch which addresses comments made by merwok via rietveld. ---------- Added file: http://bugs.python.org/file23184/issue12943-2.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12943> _______________________________________

1 0

[issue12982] .pyo file can't be imported unless -O is given
by Éric Araujo Sept. 17, 2011

Sept. 17, 2011

Éric Araujo <merwok(a)netwok.org> added the comment: I would not suggest to rename a .pyo to .pyc, they have different promises (if I can even say that, as they’re implementation details). ---------- nosy: +eric.araujo stage: -> needs patch title: .pyo file cannot be imported -> .pyo file can't be imported unless -O is given versions: +Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12982> _______________________________________

1 0

[issue12982] .pyo file cannot be imported
by Terry J. Reedy Sept. 16, 2011

Sept. 16, 2011

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: Eric, you can initially give a doc patch as text in a message, though an actual diff in nicer and may get action sooner. I agree that something could be added. Perhaps the quote "It is possible...." should be followed with something like "However, one must use the python -O option to search for and import .pyo files, as well as for creating them. An alternative is to rename them to .pyc." Or make whatever suggestion you think is … [View More]

1 0

Tutorial difficulty
by Chris Coen Sept. 13, 2011

Sept. 13, 2011

Dear Python Team. I am part way through the Python Tutorial v2.7.2 and have found one difficulty which I think is worth reporting as follows: Section = 7.1. Fancier Output Formatting Copy of tutorial original content (which does not work giving an error message with last line : "ValueError: zero length field name in format" ) : '!s' (apply str()) and '!r' (apply repr()) can be used to convert the value before it is formatted. >>> import math >>> print 'The value of PI is … [View More]

2 1

Documenting Python - finding a task
by Martin Stolle Sept. 13, 2011

Sept. 13, 2011

Hello, I want to help documenting Python. I already read the devguide and the documenting instructions (Still have to read the apple docs though). I also checked out the Python source and build the documentation. The problem I have is that I don't know which issue to pick. I would like to start with something easy in order to understand the whole process of submitting, reviewing etc. Thank you for your help and time. Kind regards Martin

2 1

doc files?
by Silke Biermann Sept. 12, 2011

Sept. 12, 2011

Dear administrator, I am trying to download the python docs at http://docs.python.org/py3k/download.html but I am getting an error (file cannot be read). Thanks! Silke

2 1

[issue7798] Make generally useful pydoc functions public
by Raymond Hettinger Sept. 11, 2011

Sept. 11, 2011

Raymond Hettinger <raymond.hettinger(a)gmail.com> added the comment: Resist the urge to fatten APIs until you're sure that: * they are needed * they are well developed (many internal utils fail this test) * they are worth the extra time it takes to learn what is in a module (adding rarely needed tools has the side-effect of obscuring things people actually need) Georg's advice is spot on. There are a lot of little internal routines in the standard library that aren't sufficiently fit … [View More]

1 0

[issue12943] tokenize: add python -m tokenize support back
by Meador Inge Sept. 11, 2011

Sept. 11, 2011

Meador Inge <meadori(a)gmail.com> added the comment: Patch against tip. ---------- assignee: -> docs@python components: +Documentation keywords: +needs review, patch nosy: +docs@python stage: needs patch -> patch review Added file: http://bugs.python.org/file23127/issue12943.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12943> _______________________________________

1 0