Mailman 3 June 2010 - docs

[issue8953] Syntax error in http://docs.python.org/library/decimal.html#recipes
by Jean Jordaan 09 Jun '10

09 Jun '10

New submission from Jean Jordaan <jean.jordaan(a)gmail.com>: http://docs.python.org/library/decimal.html#recipes has this code: for i in range(places): build(next() if digits else '0') Mismatched parenthesis. ---------- assignee: docs@python components: Documentation messages: 107396 nosy: Jean.Jordaan, docs@python priority: normal severity: normal status: open title: Syntax error in http://docs.python.org/library/decimal.html#recipes versions: Python 2.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8953> _______________________________________

2 2

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

09 Jun '10

STINNER Victor <victor.stinner(a)haypocalc.com> added the comment: Big patch: - replace Python types by C Python types (eg. str => PyUnicodeObject* and None => Py_None) - fix "w" / "w*" / "w#" doc: similar to "y" / "y*" / "y#" (and not "s" / "s*" / "s#") - add quotes to the formats, eg. s => "s" - use :ctype: to add links to some terms (eg. Py_BEGIN_ALLOW_THREADS) and use a fixed width font - replace "the default encoding" by "'utf-8' encoding" - replace true by 1, and false by 0 (C API of Python doesn't use stdbool.h but classic int) - use a list for the two modes of "es#" - Py_BuildValue(), "s" and "s#" formats: specify that the Python object is a str 1 and 0 were formatted with ``1`` and ``0``. I don't understand why, so I removed the italic style. Sorry for the length of the patch, but it was easy to work on only one aspect. ---------- keywords: +patch Added file: http://bugs.python.org/file17593/c_api_arg.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8939> _______________________________________

3 4

How to preview ReST documentation changes?
by Tal Einat 09 Jun '10

09 Jun '10

I can't seem to find a simple how-to on this anywhere. I just want to make some changes to the Python docs and view them before submitting a patch. I understand I need to use Sphinx, but how exactly to do this (including how to configure it properly for the Python docs format) I just can't tell.

2 1

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

08 Jun '10

STINNER Victor <victor.stinner(a)haypocalc.com> added the comment: Other changes of the patch: - "u#": remove "Non-Unicode objects are handled by interpreting their read-buffer pointer ...", it's no more true - "es", "es#": remove "... and objects convertible to Unicode into a character buffer", it's no more true - Py_BuildValue(), "K" and "L" formats: specify the name of the C type on Windows (_int64 / unsigned _int64) as done for PyArg_Parse*() long long types If the patch is too long, I can try to split it into smaller parts. ---------- _______________________________________ 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 Fred L. Drake, Jr. 08 Jun '10

08 Jun '10

Changes by Fred L. Drake, Jr. <fdrake(a)acm.org>: ---------- nosy: +fdrake _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8939> _______________________________________

1 0

[issue8907] time module documentation differs in trunk and py3k
by Alexander Belopolsky 08 Jun '10

08 Jun '10

Alexander Belopolsky <belopolsky(a)users.sourceforge.net> added the comment: Merged r81489 to py3k (r81840), but this affects datetime module docs, not time. On a closer examination, the differences in time.rst are correct. ---------- resolution: -> invalid status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8907> _______________________________________

1 0

[issue8907] time module documentation differs in trunk and py3k
by Mark Dickinson 08 Jun '10

08 Jun '10

Mark Dickinson <dickinsm(a)gmail.com> added the comment: r81489 should probably also be svnmerged to py3k before applying this doc change. (As far as I can tell, this is the only outstanding unmerged trunk change.) ---------- nosy: +mark.dickinson _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8907> _______________________________________

1 0

[issue8907] time module documentation differs in trunk and py3k
by Alexander Belopolsky 08 Jun '10

08 Jun '10

Alexander Belopolsky <belopolsky(a)users.sourceforge.net> added the comment: .. also 3.x does not track versionadded from 2.x ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8907> _______________________________________

1 0

[issue8907] time module documentation differs in trunk and py3k
by Alexander Belopolsky 08 Jun '10

08 Jun '10

Alexander Belopolsky <belopolsky(a)users.sourceforge.net> added the comment: There seems to be a few legitimate differences such as "int or long" vs. integer, or parenthesis for print. Patch is forthcoming. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8907> _______________________________________

1 0

[issue8939] Use C type names (PyUnicode etc; ) in the C API docs
by Antoine Pitrou 08 Jun '10

08 Jun '10

Changes by Antoine Pitrou <pitrou(a)free.fr>: ---------- nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8939> _______________________________________

1 0