Mailman 3 June 2010 - docs

[issue8151] [patch] convenience links for subprocess.call()
by Georg Brandl 05 Jun '10

05 Jun '10

Georg Brandl <georg(a)python.org> added the comment: Already done AFAICS. ---------- resolution: -> fixed status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8151> _______________________________________

1 0

[issue1635217] Add example of distutils setup() with "requires" argument
by anatoly techtonik 05 Jun '10

05 Jun '10

anatoly techtonik <techtonik(a)gmail.com> added the comment: Neal, why a piece from issue1635217#msg31028 doesn't qualify as an example? It seems that this issue may become obsolete with new packaging guide coming up. ---------- components: +Distutils, Distutils2 nosy: +docs@python versions: +Python 2.7, Python 3.3 -Python 2.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue1635217> _______________________________________

1 0

[issue8519] [patch] doc: termios and ioctl reference links
by anatoly techtonik 05 Jun '10

05 Jun '10

Changes by anatoly techtonik <techtonik(a)gmail.com>: ---------- nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8519> _______________________________________

1 0

[issue8151] [patch] convenience links for subprocess.call()
by anatoly techtonik 05 Jun '10

05 Jun '10

anatoly techtonik <techtonik(a)gmail.com> added the comment: easy, just waits to be ported ---------- nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8151> _______________________________________

1 0

[issue7229] Manual entry for time.daylight can be misleading
by R. David Murray 05 Jun '10

05 Jun '10

Changes by R. David Murray <rdmurray(a)bitdance.com>: ---------- title: [PATCH] Manual entry for time.daylight can be misleading -> Manual entry for time.daylight can be misleading _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue7229> _______________________________________

1 0

[issue7229] [PATCH] Manual entry for time.daylight can be misleading
by anatoly techtonik 05 Jun '10

05 Jun '10

anatoly techtonik <techtonik(a)gmail.com> added the comment: issue8907 seems related. ---------- nosy: +belopolsky, docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue7229> _______________________________________

1 0

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

05 Jun '10

Changes by Alexander Belopolsky <belopolsky(a)users.sourceforge.net>: ---------- nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8907> _______________________________________

1 0

[issue8899] Add docstrings to time.struct_time
by Alexander Belopolsky 05 Jun '10

05 Jun '10

New submission from Alexander Belopolsky <belopolsky(a)users.sourceforge.net>: The time.struct_time class is missing class and field docstrings: >>> time.struct_time.__doc__ is None True >>> time.struct_time.tm_year.__doc__ is None True This is significant because it is not obvious that field values are different from those of C language struct tm fields with the same names. (While module level docstring describes the timetuple, it does not list the names of the struct_time fields or mentions struct_time.) With the attached patch, >>> from time import * >>> localtime() time.struct_time(tm_year=2010, tm_mon=6, tm_mday=4, tm_hour=15, tm_min=27, tm_sec=15, tm_wday=4, tm_yday=155, tm_isdst=1) >>> help(_) Help on struct_time object: time.struct_time = class struct_time(__builtin__.object) | The time value as returned by gmtime(), localtime(), and strptime(), and accepted | by asctime(), mktime() and strftime(), may be considered as a sequence of 9 integers. | Note that several fields' values are not the same as those defined by the C language | standard for struct tm. For example, the value of tm_year is the actual year, not | year - 1900. See individual fields' descriptions for details. ... | ---------------------------------------------------------------------- | Data descriptors defined here: | | tm_hour | hours, range [0 - 23] | | tm_isdst | 1 if summer time is in effect, 0 if not, and -1 if cannot be determined | | tm_mday | day of month, range [1 - 31] | | tm_min | minutes, range [0 - 59] | | tm_mon | month of year, range [1 - 12] | | tm_sec | seconds, range [0 - 61]) | | tm_wday | day of week, range [0,6], Monday is 0 | | tm_yday | day of year, range [1,366] | | tm_year | year, for example, 1993 | | ---------------------------------------------------------------------- ---------- assignee: belopolsky components: Documentation files: struct_time_doc.diff keywords: easy, patch messages: 107089 nosy: belopolsky, docs@python, mark.dickinson priority: normal severity: normal stage: commit review status: open title: Add docstrings to time.struct_time type: feature request versions: Python 2.7, Python 3.2 Added file: http://bugs.python.org/file17556/struct_time_doc.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8899> _______________________________________

2 5

[issue8890] Modules have dangerous examples in documentation
by Terry J. Reedy 04 Jun '10

04 Jun '10

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: Henri, the owasp link you gave in your opening post now gives Bad Title error msg. ---------- nosy: +tjreedy _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8890> _______________________________________

1 0

[issue8895] newline vs. newlines in io module
by R. David Murray 04 Jun '10

04 Jun '10

R. David Murray <rdmurray(a)bitdance.com> added the comment: This is off topic for this issue, but what you just reported makes no sense to me. TextIOWrapper calls the encoder corresponding to the specified encoding in its write method. That said, it is true that the IO docs are currently a class reference and not a user reference, and this should be fixed. There may even already be an open issue for this. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8895> _______________________________________

1 0