Mailman 3 May 2013 - docs

Re: [docs] Code, test, and doc review for PEP-0435 Enum (issue 17947)
by berker.peksag＠gmail.com May 10, 2013

May 10, 2013

http://bugs.python.org/review/17947/diff/8105/Lib/enum.py File Lib/enum.py (right): http://bugs.python.org/review/17947/diff/8105/Lib/enum.py#newcode17 Lib/enum.py:17: Nit: Two blank lines. (see PEP 8 E302) http://bugs.python.org/review/17947/diff/8105/Lib/enum.py#newcode18 Lib/enum.py:18: class StealthProperty(): Is there a reason not to write `class StealthProperty:` (without the brackets) here? http://bugs.python.org/review/17947/

1 0

Code, test, and doc review for PEP-0435 Enum (issue 17947)
by eliben＠gmail.com May 10, 2013

May 10, 2013

http://bugs.python.org/review/17947/diff/8105/Lib/enum.py File Lib/enum.py (right): http://bugs.python.org/review/17947/diff/8105/Lib/enum.py#newcode2 Lib/enum.py:2: ========= Yeah, remove this :-) http://bugs.python.org/review/17947/diff/8105/Lib/enum.py#newcode19 Lib/enum.py:19: """ PEP257-ify http://bugs.python.org/review/17947/diff/8105/Lib/enum.py#newcode23 Lib/enum.py:23: # Used to provide access to the `name` and `value` properties of enum This class is quite generic though, and … [View More]

1 0

[issue5901] missing meta-info in documentation pdf
by A.M. Kuchling May 10, 2013

May 10, 2013

A.M. Kuchling added the comment: This seems to be fixed now. I downloaded python-3.3.1-docs-pdf-letter.tar.bz2 and ran pdfinfo on using.pdf: Title: Python Setup and Usage Subject: Keywords: Author: Guido van Rossum, Fred L. Drake, Jr., editor Creator: LaTeX with hyperref package Producer: pdfTeX-1.40.10 CreationDate: Fri May 10 09:42:17 2013 ModDate: Fri May 10 09:42:17 2013 Tagged: no Pages: 65 Encrypted: no Page … [View More]

1 0

[issue17841] Remove missing aliases from codecs documentation
by Nick Coghlan May 10, 2013

May 10, 2013

Nick Coghlan added the comment: For anyone else reading the issue and wondering about Ezio's question above - this issue was actually spun out from issue 7475, which covers the long saga of getting these codecs fully restored in the new world order of Python 3 :) ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17841> _______________________________________

1 0

[issue17841] Remove missing aliases from codecs documentation
by Ezio Melotti May 10, 2013

May 10, 2013

Ezio Melotti added the comment: Fixed, thanks for the patch! @Nick While this works as a short-term solution, I think it would be good to 1) reintroduce the aliases in 3.4 (so that codecs.encode(b'foo', 'base64') works without spelling out the full codec name); 2) either separate these codecs from the others, or tweak the error message of str.encode/bytes.decode to point to codecs.encode/decode. Should I create a new issue and/or ask python-dev about this? ---------- assignee: docs@python -… [View More]

1 0

[issue17841] Remove missing aliases from codecs documentation
by Roundup Robot May 10, 2013

May 10, 2013

Roundup Robot added the comment: New changeset ead47bc3a763 by Ezio Melotti in branch '3.3': #17841: remove missing codecs aliases from the documentation. Patch by Thomas Fenzl. http://hg.python.org/cpython/rev/ead47bc3a763 New changeset eafff38a56cc by Ezio Melotti in branch 'default': #17841: merge with 3.3. http://hg.python.org/cpython/rev/eafff38a56cc ---------- nosy: +python-dev _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17841> _______________________________________

1 0

[issue14878] send statement from PEP342 is poorly documented.
by Stephen Lacy May 10, 2013

May 10, 2013

New submission from Stephen Lacy <slacy(a)slacy.com>: There's reasonable documentation of the yield statement for most python versions under Section 6: Simple Statements, particularly 6.8 "The Yield Statement" (http://docs.python.org/release/2.7/reference/simple_stmts.html#the-yield-st…) But, there's no mention of the return value of the yield statement, or that the send statement even exists. It's mentioned in passing here under "PEP342 New Generator Features" (http://docs.python.org/… [View More]

6 6

Broken link in http://docs.python.org/2/install/index.html
by Joe Aikkaravelil May 9, 2013

May 9, 2013

I found a broken link in http://docs.python.org/2/install/index.html#older-versions-of-python-and-mi… "Older Versions of Python and MinGW¶<http://docs.python.org/2/install/index.html#older-versions-of-python-and-mi…> The following instructions only apply if you’re using a version of Python inferior to 2.4.1 with a MinGW inferior to 3.0.0 (with binutils-2.13.90-20030111-1). These compilers require some special libraries. This task is more complex than for Borland’s C++, because there is … [View More]

1 0

[issue17858] Different documentation for identical methods
by Andriy Mysyk May 9, 2013

May 9, 2013

New submission from Andriy Mysyk: Use _thread.Lock.acquire() documentation for threading.Lock.acquire(). threading.Lock inherits acquire() method from _thread.Lock. The two acquire() methods are identical in their functionality yet have different documentation. Documentation for threading.Lock.acquire() creates the impression that the function is more complex or harder to use than it actually is. See http://docs.python.org/devguide/documenting.html#economy-of-expression for guidelines. -----… [View More]

3 8

[issue17938] Duplicate text in docs/reference/import statement
by Stefan Chrobot May 9, 2013

May 9, 2013

New submission from Stefan Chrobot: http://docs.python.org/3/reference/simple_stmts.html#the-import-statement After the "Examples", there's a duplicated paragraph: The public names defined by a module are determined by checking the module’s namespace for a variable named __all__; if defined, it must be a sequence of strings which are names defined or imported by that module. The names given in __all__ are all considered public and are required to exist. If __all__ is not defined, the set of … [View More]

3 3