Mailman 3 February 2012 - docs

[issue13996] "What's New in Python" should have initial release date on heading
by Tshepang Lekhonkhobe 11 Feb '12

11 Feb '12

New submission from Tshepang Lekhonkhobe <tshepang(a)gmail.com>: As an example, the date near the top of this document http://docs.python.org/py3k/whatsnew/3.0.html matches that of today, which can be misleading (it appears as if the thing was released today). Also, by initial release, I mean the first "final", not the point release. Maybe any other date mentioned would perhaps be the date the docs were updated, *not* the date they were rebuilt. ---------- assignee: docs@python components: Documentation messages: 153138 nosy: docs@python, tshepang priority: normal severity: normal status: open title: "What's New in Python" should have initial release date on heading type: enhancement versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13996> _______________________________________

4 3

some example code uses a parameter called "next", resulting in a name conflict
by Winston C. Yang 10 Feb '12

10 Feb '12

The code below has an issue: the __init__ method has a parameter called "next", which conflicts with the built-in "next" in Python. In the link, the "next" parameter is syntax-colored green instead of black, showing its special status. Winston http://docs.python.org/py3k/tutorial/errors.html 8.5 User-defined Exceptions class TransitionError(Error): """Raised when an operation attempts a state transition that's not allowed. Attributes: previous -- state at beginning of transition next -- attempted new state message -- explanation of why the specific transition is not allowed """ def __init__(self, previous, next, message): self.previous = previous self.next = next self.message = message

1 0

[issue13865] distutils documentation says Extension has "optional" argument
by Éric Araujo 09 Feb '12

09 Feb '12

Éric Araujo <merwok(a)netwok.org> added the comment: Fixed, cheers! ---------- resolution: -> fixed stage: -> committed/rejected status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13865> _______________________________________

1 0

[issue13865] distutils documentation says Extension has "optional" argument
by Roundup Robot 09 Feb '12

09 Feb '12

Roundup Robot <devnull(a)psf.upfronthosting.co.za> added the comment: New changeset cf1c466ee9e0 by Éric Araujo in branch '2.7': distutils 2.7’s Extension does not support optional (#13865). http://hg.python.org/cpython/rev/cf1c466ee9e0 ---------- nosy: +python-dev _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13865> _______________________________________

1 0

[issue9442] Update sys.version doc
by Éric Araujo 09 Feb '12

09 Feb '12

New submission from Éric Araujo <merwok(a)netwok.org>: Attaching a patch to edit mention of “build number” in library/sys. I also don’t understand “The first three characters are used to identify the version in the installation directories (where appropriate on each platform)”, maybe someone who does could enlighten me. If #5778 is rejected, the doc will need another update to mention that there may be a newline in sys.version. ---------- assignee: docs@python components: Documentation files: sys.version1.diff keywords: patch messages: 112189 nosy: docs@python, merwok priority: normal severity: normal stage: patch review status: open title: Update sys.version doc versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 Added file: http://bugs.python.org/file18289/sys.version1.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9442> _______________________________________

4 9

[issue9021] no copy.copy problem description
by anatoly techtonik 09 Feb '12

09 Feb '12

New submission from anatoly techtonik <techtonik(a)gmail.com>: `copy` module covers very important aspect of Python programming. However its documentation doesn't provide any intro or overview of this problem starting right from details. When people meet `copy` construction in the code - the refer to module documentation and its doesn't completely answer two basic questions they have: 1. why copy module is needed (i.e. what's the problem with var assignment) 2. when and where it should be used ---------- assignee: docs@python components: Documentation messages: 108069 nosy: docs@python, techtonik priority: normal severity: normal status: open title: no copy.copy problem description versions: Python 2.7, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9021> _______________________________________

5 10

[issue1040439] Missing documentation on how to link with libpython
by Eli Bendersky 08 Feb '12

08 Feb '12

Eli Bendersky <eliben(a)gmail.com> added the comment: ISTM that part of the doc specifically deals with Unix, so this issue can be closed as completed. Windows is a different issue. Perhaps the documentation should have a new section on embedding on Windows, similarly to the "Building C and C++ Extensions on Windows" section in the "extending" documentation. Anyway, if there's interest in that, it should be a separate issue. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue1040439> _______________________________________

1 0

[issue8255] Packaging step-by-step tutorial
by Tshepang Lekhonkhobe 06 Feb '12

06 Feb '12

Changes by Tshepang Lekhonkhobe <tshepang(a)gmail.com>: ---------- nosy: +tshepang _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8255> _______________________________________

1 0

[issue13951] Seg Fault in .so called by ctypes causes the interpreter to Seg Fault
by Amaury Forgeot d'Arc 06 Feb '12

06 Feb '12

Amaury Forgeot d'Arc <amauryfa(a)gmail.com> added the comment: [Please do not change issue titles - your recommendation was enough] Indeed, incorrect usage of ctypes can crash the program, and there is nothing Python can do. But I could not find any warning about this in the documentation, except maybe this sentence: "There are, however, enough ways to crash Python with ctypes, so you should be careful anyway." Let's turn this into a doc issue, then. ---------- assignee: -> docs@python components: +Documentation nosy: +amaury.forgeotdarc, docs@python title: please close - Seg Fault in .so called by ctypes causes the interpreter to Seg Fault -> Seg Fault in .so called by ctypes causes the interpreter to Seg Fault _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13951> _______________________________________

1 0

[issue1040439] Missing documentation on how to link with libpython
by Antoine Pitrou 06 Feb '12

06 Feb '12

Antoine Pitrou <pitrou(a)free.fr> added the comment: > Is there still work to do on this issue? Not for Unix, no. I don't if it's applicable to Windows. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue1040439> _______________________________________

1 0