Mailman 3 February 2011 - docs

[issue901727] extra_path kwarg to setup() undocumented
by Éric Araujo 13 Feb '11

13 Feb '11

Éric Araujo <merwok(a)netwok.org> added the comment: You shouldn’t have :) apiref.rst is very outdated in d2, because the setup function does not exist. The docs could be adjusted to document Distribution instead of setup, but we’re not even sure Distribution will stay. I think I will make a compromise here and apply the patch to distutils1 doc, so that the information is found on the official docs. ---------- components: +Distutils -Distutils2 versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3 -3rd party _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue901727> _______________________________________

2 1

[issue901727] extra_path kwarg to setup() undocumented
by Alexis Metaireau 13 Feb '11

13 Feb '11

Alexis Metaireau <ametaireau(a)gmail.com> added the comment: I've applied the patch on distutils2. This can now be closed. ---------- nosy: +alexis _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue901727> _______________________________________

1 0

[issue11076] Iterable argparse Namespace
by Steven Bethard 11 Feb '11

11 Feb '11

Steven Bethard <steven.bethard(a)gmail.com> added the comment: There's no argparse in 3.1, so it should only go into 2.7, 3.2 and 3.3. But yes, the patch looks great to me too. ---------- versions: -Python 3.1 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11076> _______________________________________

1 0

[issue11076] Iterable argparse Namespace
by Éric Araujo 10 Feb '11

10 Feb '11

Éric Araujo <merwok(a)netwok.org> added the comment: +1 for this patch. Documentation fixes are backported from the development branch to stable branches, so yes, this will land in 3.1 too. ---------- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python type: feature request -> versions: +Python 2.7, Python 3.1, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11076> _______________________________________

1 0

[issue11151] Arguments to various types not specified in types module
by Noufal 08 Feb '11

08 Feb '11

New submission from Noufal <noufal(a)nibrahim.net.in>: The documentation for the types module seems to have an obvious bug. The arguments to create the various types are not mentioned in the docs page on http://docs.python.org/library/types.html This came to my attention from a stack overflow question here http://stackoverflow.com/questions/4933325/where-can-i-find-documentation-f… ---------- assignee: docs@python components: Documentation messages: 128175 nosy: docs@python, noufal priority: normal severity: normal status: open title: Arguments to various types not specified in types module type: behavior versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11151> _______________________________________

3 2

[issue11141] 2.x range() in 3.x shelve documentation
by Daniel Urban 07 Feb '11

07 Feb '11

New submission from Daniel Urban <urban.dani+py(a)gmail.com>: The example in the shelve documentation (http://docs.python.org/dev/py3k/library/shelve.html#example) uses the old range() (which returned a list): d['xx'] = range(4) # this works as expected, but... d['xx'].append(5) # *this doesn't!* -- d['xx'] is STILL range(4)! ---------- assignee: docs@python components: Documentation messages: 128138 nosy: docs@python, durban priority: normal severity: normal status: open title: 2.x range() in 3.x shelve documentation versions: Python 3.1, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11141> _______________________________________

4 3

[issue11137] clarify use of imaplib IMAP4(_SSL) shutdown
by John 07 Feb '11

07 Feb '11

New submission from John <jh45dev(a)gmail.com>: Attempting IMAP4_SSL.shutdown() after IMAP4_SSL.logout() throws an error because the socket is already closed. (I cannot test with plain IMAP4.) Please add appropriate notice, perhaps under IMAP4.shutdown(). Perhaps something like "If you do not use open(), and do only login() and logout(), you do not need shutdown(), as logout() does it for you." -- jh ---------- assignee: docs@python components: Documentation messages: 128096 nosy: docs@python, jh45 priority: normal severity: normal status: open title: clarify use of imaplib IMAP4(_SSL) shutdown versions: Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11137> _______________________________________

3 2

[issue8691] Doc: left alignment is not the default for numbers
by Terry J. Reedy 07 Feb '11

07 Feb '11

New submission from Terry J. Reedy <tjreedy(a)udel.edu>: As reported on python-list by Alan G Isaac, Lib Ref 6.1.3.1. Format Specification Mini-Language, for instance http://docs.python.org/dev/py3k/library/string.html#formatstrings wrongly says in the alignment section "'<' Forces the field to be left-aligned within the available space (This is the default.)" This latter, of course, is not true for number fields. "(This is the default.)" could be replaced by "(the string default)." (in any case, the '.' should be outside the () unless one is added after 'space' before '(') and "(the number default)" added to the next line. Or instead the issue of defaults could be addressed in the text below the table. I am assuming that this issue affects 2.6/7. ---------- assignee: docs@python components: Documentation messages: 105536 nosy: docs@python, tjreedy priority: normal severity: normal status: open title: Doc: left alignment is not the default for numbers versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8691> _______________________________________

4 5

[issue11138] Docs: incollect example: "fill" and "align"
by Urago Keisuke 07 Feb '11

07 Feb '11

New submission from Urago Keisuke <bravo(a)resourcez.org>: "Nesting arguments and more complex examples" at http://docs.python.org/library/string.html#format-examples Below example code is no errors: >>> for align, text in zip('<^>', ['left', 'center', 'right']): ... '{0:{align}{fill}16}'.format(text, fill=align, align=align) I think meaning is as follows: ... '{0:{fill}{align}16}'.format(text, fill=align, align=align) ---------- assignee: docs@python components: Documentation messages: 128099 nosy: Urago.Keisuke, docs@python priority: normal severity: normal status: open title: Docs: incollect example: "fill" and "align" 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/issue11138> _______________________________________

2 1

[issue11090] Doc errors for unittest in Python 3.1
by Éric Araujo 06 Feb '11

06 Feb '11

Changes by Éric Araujo <merwok(a)netwok.org>: Removed file: http://bugs.python.org/file20657/fix-11090.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11090> _______________________________________

1 0