Mailman 3 - docs - python.org

[issue8340] bytearray undocumented on trunk
by Antoine Pitrou 21 Jun '10

21 Jun '10

Antoine Pitrou <pitrou(a)free.fr> added the comment: 'bytes' is an alias for 'str' in 2.x, so it shouldn't be "documented" separately. As for bytearray, yes, it should be added if not present. ---------- nosy: +pitrou _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8340> _______________________________________

1 0

[issue8340] bytearray undocumented on trunk
by Mark Dickinson 21 Jun '10

21 Jun '10

Mark Dickinson <dickinsm(a)gmail.com> added the comment: Ideally, there should be documentation of 'bytes' and 'bytearray' in the 'Built-in Types' section of the library manual, too. (library/stdtypes.rst). ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8340> _______________________________________

1 0

[issue8340] bytearray undocumented on trunk
by Éric Araujo 21 Jun '10

21 Jun '10

Changes by Éric Araujo <merwok(a)netwok.org>: ---------- assignee: georg.brandl -> docs@python nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8340> _______________________________________

1 0

bug report: multiprocessing module
by Greenpickle 20 Jun '10

20 Jun '10

In particular, the section on Windows (16.6.3.2, the version at http://docs.python.org/library/multiprocessing.html#windows, if there happen to be others). It mentions that the 'main module' must be able to be 'safely imported', but doesn't make it clear that it needs the .py extension, so that it can be imported at all. Just thought it might help others where I spent a few minutes trying to work out what was going wrong.

1 0

[issue8939] Use C type names (PyUnicode etc; ) in the C API docs
by STINNER Victor 20 Jun '10

20 Jun '10

STINNER Victor <victor.stinner(a)haypocalc.com> added the comment: > Shouldn’t “inside a :ctype:`Py_BEGIN_ALLOW_THREADS` block” rather use “:cmacro:”? Same remark on IRC: "Taggnostr> haypo, in r82084: "Add :ctype: to Py_BEGIN_ALLOW_THREADS and int", maybe :cfunc: (or :cmacro:)?" I don't know :cmacro:. I will fix it in my next patch. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8939> _______________________________________

1 0

[issue8939] Use C type names (PyUnicode etc; ) in the C API docs
by Éric Araujo 19 Jun '10

19 Jun '10

Éric Araujo <merwok(a)netwok.org> added the comment: Shouldn’t “inside a :ctype:`Py_BEGIN_ALLOW_THREADS` block” rather use “:cmacro:”? ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8939> _______________________________________

1 0

[issue5005] 3.0 sqlite doc: most examples refer to pysqlite2, use 2.x syntax.
by Terry J. Reedy 19 Jun '10

19 Jun '10

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: This issue is about the examples in 11.6.1. Module functions and constants. All 3 points are fixed. The indentation issue seems to have been fixed by making the blank line completely blank with no spaces. I would have removed it, but cut and paste now works. I have no idea what Google has to do with this, but thanks for pinging it. ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python resolution: -> fixed status: open -> closed type: -> behavior versions: +Python 3.1 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue5005> _______________________________________

1 0

[issue8939] Use C type names (PyUnicode etc; ) in the C API docs
by STINNER Victor 19 Jun '10

19 Jun '10

STINNER Victor <victor.stinner(a)haypocalc.com> added the comment: r82084 (in 3.2 and r82085 in 3.1) fixes some of the reported issues. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8939> _______________________________________

1 0

[issue9024] PyDateTime_IMPORT macro incorrectly marked up
by Tim Golden 18 Jun '10

18 Jun '10

Changes by Tim Golden <mail(a)timgolden.me.uk>: ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python stage: -> patch review versions: +Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9024> _______________________________________

1 0

[issue8937] SimpleHTTPServer should contain usage example
by anatoly techtonik 17 Jun '10

17 Jun '10

New submission from anatoly techtonik <techtonik(a)gmail.com>: Currently SimpleHTTPServer docs contains phrase "For example usage, see the implementation of the test() function." with no reference where this test() function is located. This is not user friendly. ---------- assignee: docs@python components: Documentation messages: 107304 nosy: docs@python, techtonik priority: normal severity: normal status: open title: SimpleHTTPServer should contain usage example versions: Python 2.6, Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8937> _______________________________________

2 6