Mailman 3 June 2010 - docs

[issue9132] Documentation for comparing dictionaries is out of date
by Daniel Stutzbach 14 Jul '10

14 Jul '10

New submission from Daniel Stutzbach <daniel(a)stutzbachenterprises.com>: reference/expressions.html#notin reads: "Mappings (dictionaries) compare equal if and only if their sorted (key, value) lists compare equal. [4] Outcomes other than equality are resolved consistently, but are not otherwise defined. [5]" However, the last sentence is no longer true. I suggest changing the last sentence to: "Comparisons other than equality testing raise a TypeError." I think the footnote [5] is sufficiently historical that it could be removed as well. Alternately, it could be updated to read, "In older versions of Python, outcomes other than equality were resolved consistently but were not otherwise defined." ---------- assignee: docs@python components: Documentation messages: 109009 nosy: docs@python, stutzbach priority: normal severity: normal stage: needs patch status: open title: Documentation for comparing dictionaries is out of date versions: Python 3.1, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9132> _______________________________________

6 11

[issue8564] Update documentation on doctest/unittest2 integration
by Peter Fein 10 Jul '10

10 Jul '10

New submission from Peter Fein <pfein(a)pobox.com>: The documentation on integrating doctests in a file of unittests is confusing and out of date. This patch updates the documentation to use unittest2 test discovery. ---------- assignee: docs@python components: Documentation files: doctest_unittest_integration_doc.diff keywords: patch messages: 104468 nosy: docs@python, pfein priority: normal severity: normal status: open title: Update documentation on doctest/unittest2 integration versions: Python 2.7, Python 3.3 Added file: http://bugs.python.org/file17123/doctest_unittest_integration_doc.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8564> _______________________________________

5 6

[issue8946] PyBuffer_Release signature in 3.1 documentation is incorrect
by Dave Opstad 08 Jul '10

08 Jul '10

New submission from Dave Opstad <dave.opstad(a)monotypeimaging.com>: According to the 3.1 documentation, the prototype for PyBuffer_Release is: void PyBuffer_Release(PyObject *obj, Py_buffer *view); However, abstract.h has this prototype: PyAPI_FUNC(void) PyBuffer_Release(Py_buffer *view); The documentation's reference to "obj" should be removed. ---------- assignee: docs@python components: Documentation messages: 107342 nosy: docs@python, opstad priority: normal severity: normal status: open title: PyBuffer_Release signature in 3.1 documentation is incorrect type: behavior versions: Python 3.1 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8946> _______________________________________

3 2

spelling typo in 2to3 module description
by Richard Mathar 04 Jul '10

04 Jul '10

In http://docs.python.org/library/2to3.html#2to3fixer-long the name of the fixer "raises" should be "raise" , singular of the word. -- Richard J. Mathar cell phone (+49) (0) 177 3834227 (E-plus) Sterrewacht Universiteit Leiden Fax (+31) (0) 71 527 5819 Postbus 9513 2300RA Leiden E-mail mathar(a)strw.leidenuniv.nl r.j.mathar(a)umail.leidenuniv.nl The Netherlands URL http://www.strw.leidenuniv.nl/~mathar office: Niels Bohrweg 2, 2333 CA Leiden, H104

2 2

[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers
by Benjamin Ryzman 30 Jun '10

30 Jun '10

Benjamin Ryzman <benjamin+python(a)ryzman.fr> added the comment: Content of the above pastie: Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56) [GCC 4.4.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import signal >>> import subprocess >>> signal.signal(signal.SIGCHLD,signal.SIG_IGN) 0 >>> subprocess.Popen(["echo","blah"], stdout=subprocess.PIPE).communicate()[0] Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.6/subprocess.py", line 698, in communicate self.wait() File "/usr/lib/python2.6/subprocess.py", line 1170, in wait pid, sts = _eintr_retry_call(os.waitpid, self.pid, 0) File "/usr/lib/python2.6/subprocess.py", line 465, in _eintr_retry_call return func(*args) OSError: [Errno 10] No child processes >>> oldsignal = signal.signal(signal.SIGCHLD,signal.SIG_DFL) >>> subprocess.Popen(["echo","blah"], stdout=subprocess.PIPE).communicate()[0] 'blah\n' >>> signal.signal(signal.SIGCHLD,oldsignal) 0 ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9127> _______________________________________

1 0

[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers
by Jean-Paul Calderone 30 Jun '10

30 Jun '10

Jean-Paul Calderone <exarkun(a)twistedmatrix.com> added the comment: You should include all relevant issue materials here, in the Python issue tracker. This ticket will be useless as soon as pastie.org decides to forget about your paste. ---------- nosy: +exarkun _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9127> _______________________________________

1 0

[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers
by Benjamin Ryzman 30 Jun '10

30 Jun '10

Changes by Benjamin Ryzman <benjamin+python(a)ryzman.fr>: ---------- assignee: -> docs@python components: +Documentation, Library (Lib) nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9127> _______________________________________

1 0

3.1.2 documentation for dict: iter(d) references to iteritems(), but iteritems is no longer documented.
by Jens Quade 30 Jun '10

30 Jun '10

1 0

[issue9121] Glossary entry for nested scope incorrect
by Ethan Furman 29 Jun '10

29 Jun '10

New submission from Ethan Furman <ethan(a)stoneleaf.us>: It currently states "Note that nested scopes work only for reference and not for assignment which will always write to the innermost scope." This should be updated to read, e.g. "Note that unless the new nonlocal keyword is used nested scopes work only for reference and not for assignment which will otherwise write to the innermost scope." ---------- assignee: docs@python components: Documentation messages: 108949 nosy: docs@python, stoneleaf priority: normal severity: normal status: open title: Glossary entry for nested scope incorrect versions: Python 3.1 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9121> _______________________________________

2 1

[issue9114] br"" string literals don't appear to be documented
by Mark Summerfield 29 Jun '10

29 Jun '10

New submission from Mark Summerfield <mark(a)qtrac.eu>: It appears that br"" (raw bytes) isn't documented, at least not along with string and bytes literals: http://docs.python.org/py3k/reference/lexical_analysis.html#literals Yet they are supported: http://mail.python.org/pipermail/python-ideas/2010-June/007529.html ---------- assignee: docs@python components: Documentation messages: 108902 nosy: docs@python, mark priority: normal severity: normal status: open title: br"" string literals don't appear to be documented versions: Python 3.1, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9114> _______________________________________

4 3