Mailman 3 October 2013 - docs

[bug] Another error message (documentation)
by Pavel Fedotov 06 Oct '13

06 Oct '13

Python 3.3, documentation: http://docs.python.org/3.3/tutorial/errors.html#exceptions First expression output another error message: >>> 10 * (1/0) Traceback (most recent call last): File "<stdin>", line 1, in <module> ZeroDivisionError: division by zero (instead of ... File "<stdin>", line 1, in ? ZeroDivisionError: int division or modulo by zero that documentation reports) -- Pavel Fedotov

2 1

Python2orPython3 sites dormant modules as a reason not to move to Python3
by Christian Clauss 06 Oct '13

06 Oct '13

https://wiki.python.org/moin/Python2orPython3 currently says: "Popular modules that don't yet support Python 3 include Twisted (for networking and other applications), gevent (like Twisted, but different), and PIL (for processing images)." But this obscures the reality that gevent and PIL are both dormant. There have been no gevent updates posted to pypi for more than a year. There have been no PIL updates in 4 years and the "friendly" fork named "Pillow" does support both Python 2 and 3 with similar or improved functionality. The Twisted community has work to do to but is already on a path to Python 3 compatibility. Pillow: https://pypi.python.org/pypi/Pillow/2.1.0 Python2or3 also says: "For creating GUI applications Python 3 [...] has been supported by PyQt4 almost from the day Python 3 was released." This will push potential users to the older PyQT4 instead of the more modern PyQT5. https://pypi.python.org/pypi/PyQt5/5.0.1 Thanks for listening! CCC

2 5

bug in documentation
by Rajesh Panigrahi 06 Oct '13

06 Oct '13

Hello Team, There need a small correction in documentation page for "14. Floating Point Arithmetic: Issues and Limitations" Issue Description:- It has been written 0/2 + 0/4 + 1/8 = 0.001. Expected :- The mathematical calculation should be written as 0.125. Due to some problem i am not able to attach the screen shot. Regards, Rajesh

2 1

[issue19055] Regular expressions: * does not match as many repetitions as possible.
by Ezio Melotti 06 Oct '13

06 Oct '13

Changes by Ezio Melotti <ezio.melotti(a)gmail.com>: ---------- assignee: -> docs@python components: +Documentation keywords: +easy nosy: +docs@python stage: -> needs patch type: behavior -> enhancement _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19055> _______________________________________

1 0

[issue19074] Add PySide to GUI FAQ
by anatoly techtonik 06 Oct '13

06 Oct '13

New submission from anatoly techtonik: http://docs.python.org/2/faq/gui.html - this page misses info about PySide. ---------- assignee: docs@python components: Documentation messages: 198279 nosy: docs@python, techtonik priority: normal severity: normal status: open title: Add PySide to GUI FAQ versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19074> _______________________________________

7 10

[issue19069] Built-in float docstrings are not PEP-8 compatible
by Marco Buttu 05 Oct '13

05 Oct '13

New submission from Marco Buttu: As reported in the title: >>> float.as_integer_ratio.__doc__.splitlines()[2] 'Returns a pair of integers, whose ratio is exactly equal to the original' >>> float.as_integer_ratio.__doc__.splitlines()[4] 'Raises OverflowError on infinities and a ValueError on NaNs.' >>> float.conjugate.__doc__ 'Returns self, the complex conjugate of any float.' >>> float.is_integer.__doc__ 'Returns True if the float is an integer.' >>> float.__setformat__.__doc__.splitlines()[-2] 'Overrides the automatic determination of C-level floating point type.' ... They should have been 'Return...', 'Raise...' and 'Override...' Patch is attached ---------- assignee: docs@python components: Documentation files: floatobject.patch keywords: patch messages: 198246 nosy: docs@python, marco.buttu priority: normal severity: normal status: open title: Built-in float docstrings are not PEP-8 compatible type: enhancement versions: Python 3.1, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file31840/floatobject.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19069> _______________________________________

6 5

[issue19068] Some built-in complex docstrings are not PEP-8 compatible
by Marco Buttu 05 Oct '13

05 Oct '13

New submission from Marco Buttu: As reported in the title: >>> complex.conjugate.__doc__.splitlines()[-1] 'Returns the complex conjugate of its argument. (3-4j).conjugate() == 3+4j.' >>> complex.__format__.__doc__.splitlines()[-1] 'Converts to a string according to format_spec.' They should have been 'Return...' and 'Convert...'. Patch is attached ---------- assignee: docs@python components: Documentation files: complexobject.patch keywords: patch messages: 198245 nosy: docs@python, marco.buttu priority: normal severity: normal status: open title: Some built-in complex docstrings are not PEP-8 compatible versions: Python 3.1, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file31839/complexobject.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19068> _______________________________________

5 5

[issue19067] Built-in range docstrings are not PEP-8 compatible
by Marco Buttu 05 Oct '13

05 Oct '13

New submission from Marco Buttu: The range documentation is not PEP-8 compatible: >>> range.__doc__.splitlines()[-1] 'Returns a virtual sequence of numbers from start to stop by step.' >>> range.__reversed__.__doc__ 'Returns a reverse iterator.' >>> range.index.__doc__.splitlines()[-1] 'Raises ValueError if the value is not present.' They should have been 'Return...' and 'Raise...'. Patch is attached ---------- assignee: docs@python components: Documentation files: rangeobject.patch keywords: patch messages: 198244 nosy: docs@python, marco.buttu priority: normal severity: normal status: open title: Built-in range docstrings are not PEP-8 compatible type: enhancement versions: Python 3.1, Python 3.2, Python 3.3 Added file: http://bugs.python.org/file31838/rangeobject.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19067> _______________________________________

6 6

[issue16195] Difficult or impossible to figure out how garbage collector and weak references should interact for user-defined extension types
by Jean-Paul Calderone 05 Oct '13

05 Oct '13

New submission from Jean-Paul Calderone: There appears to be very little, if any, documentation about how to handle the list at tp_weaklistoffset for types supporting being weak referenced, particularly with respect to garbage collection. Who owns the list? Who owns the objects in the list? Should the list be traversed by the extension type's tp_traverse? Should it ever be INCREF'd or DECREF'd? Does tp_dealloc have any responsibilities with respect to it? >From looking at CPython's own source, it appears that tp_traverse should not touch it (Yhg1s confirmed this on #python). Cython, at least, appears to have come to an alternate conclusion though - it generates tp_traverse functions which visit the list (and provoke gc assertions to fail on Python 2.7 in debug mode). Some documentation about what is correct to do would be excellent, and would make it easier to explain to Cython developers what they're doing wrong (or confirm that they're doing something right, in which case there are some more bugs to file against the CPython stdlib, since they do something different from Cython). ---------- assignee: docs@python components: Documentation messages: 172639 nosy: docs@python, exarkun priority: normal severity: normal status: open title: Difficult or impossible to figure out how garbage collector and weak references should interact for user-defined extension types _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue16195> _______________________________________

6 5

[issue19148] Minor issues with Enum docs
by Esa Peuha 05 Oct '13

05 Oct '13

New submission from Esa Peuha: I noticed a couple of issues with the Enum documentation. First, there are some markup bugs which should be fixed by the attached file. Second, I think "If the only change desired is no aliases allowed" is very bad English and should be reworded; I would go with "If you only want to disallow aliases" but maybe other people have better ideas. ---------- assignee: docs@python components: Documentation files: enum.diff keywords: patch messages: 198869 nosy: Esa.Peuha, docs@python priority: normal severity: normal status: open title: Minor issues with Enum docs type: enhancement versions: Python 3.4 Added file: http://bugs.python.org/file31947/enum.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue19148> _______________________________________

5 4