Mailman 3 August 2012 - docs

[issue14783] Update int() docstring from manual
by Ezio Melotti Aug. 28, 2012

Aug. 28, 2012

Ezio Melotti added the comment: .. function:: int(n=0) int(s, base=10) should do the trick. +1 on using this instead of int([number | string[, base]]) ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14783> _______________________________________

1 0

[issue14042] json.dumps() documentation is slightly incorrect.
by Petri Lehtinen Aug. 28, 2012

Aug. 28, 2012

Petri Lehtinen added the comment: This is a documentation bug for 2.7. Setting as duplicate of #13769. ---------- nosy: +petri.lehtinen resolution: -> duplicate stage: needs patch -> committed/rejected status: open -> closed superseder: -> json.dump(ensure_ascii=False) return str instead of unicode versions: -Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14042> _______________________________________

1 0

[issue14880] csv.reader and .writer use wrong kwargs notation in 2.7 docs
by Hynek Schlawack Aug. 28, 2012

Aug. 28, 2012

New submission from Hynek Schlawack <hs(a)ox.cx>: It says > csv.reader(csvfile[, dialect='excel'][, fmtparam]) > csv.writer(csvfile[, dialect='excel'][, fmtparam]) in 2.7. I presume it should be like in 3.x: > csv.reader(csvfile, dialect='excel', **fmtparams) > csv.writer(csvfile, dialect='excel', **fmtparams) Or am I missing something? (I found argument renaming to be too invasive for my default-args-notation ticket #14804) ---------- assignee: docs@python components: Documentation keywords: easy messages: 161332 nosy: docs@python, hynek priority: normal severity: normal status: open title: csv.reader and .writer use wrong kwargs notation in 2.7 docs versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14880> _______________________________________

4 9

[issue11964] Undocumented change to indent param of json.dump in 3.2
by Éric Araujo Aug. 28, 2012

Aug. 28, 2012

New submission from Éric Araujo <merwok(a)netwok.org>: I found out that the indent parameter of json.dump was changed in 3.2: it can be a string as well as an int. The docstring was not updated; the reST doc was, but without a versionchanged directive. This probably applies to the doc and docstring of the classes implementing dump, too, and there may be other half-documented changes. ---------- assignee: docs@python components: Documentation, Library (Lib) keywords: easy messages: 134869 nosy: bob.ippolito, docs@python, eric.araujo, rhettinger priority: normal severity: normal stage: needs patch status: open title: Undocumented change to indent param of json.dump in 3.2 versions: Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11964> _______________________________________

7 14

[issue9694] argparse required arguments displayed under "optional arguments"
by Martin Burger Aug. 28, 2012

Aug. 28, 2012

Changes by Martin Burger <m(a)rtin-burger.net>: ---------- nosy: +mburger _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9694> _______________________________________

1 0

[issue14783] Update int() docstring from manual
by Raymond Hettinger Aug. 28, 2012

Aug. 28, 2012

Raymond Hettinger added the comment: The 3.3 version has the virtue of being accurate and the vice of being confusing. In a way, it has made the docs worse for the average user of common cases. Is there a way to stack the alternative signatures rather than mush the various used into a single pile of mush? int(x=0) --> integer coercion int(str, base=10) --> integer converted from string in a given base ---------- nosy: +rhettinger _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14783> _______________________________________

1 0

[issue9650] format codes in time.strptime docstrings
by Chris Rebert Aug. 28, 2012

Aug. 28, 2012

Chris Rebert added the comment: +1 on including am/pm-related codes. Blame us backwards, non-metric Americans. Sounds GTM otherwise. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9650> _______________________________________

1 0

[issue15790] Python 3.3.0rc1 release notes claims PEP-405 support, yet pysetup is not in the package (needs more usage documentation, to get pip working)
by Pas Aug. 27, 2012

Aug. 27, 2012

New submission from Pas: Python 3.3.0rc1 release notes ( http://python.org/download/releases/3.3.0/ ) claims PEP-405 support, yet pysetup is not in the tarball. (After reading through mailing lists and bugs it's clear that the move to "packaging" module got pulled, so it's still just distutils in there.) There is no documentation on how to get a pyvenv (or virtualenv, or any other virtual enviroment solution) built venv to gain setuptools/pip support. ---------- assignee: docs@python components: Documentation messages: 169194 nosy: docs@python, pas priority: normal severity: normal status: open title: Python 3.3.0rc1 release notes claims PEP-405 support, yet pysetup is not in the package (needs more usage documentation, to get pip working) versions: Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15790> _______________________________________

3 5

[issue12403] Mention sys.displayhook in code module docs and the compile builtin docs
by Aaron Iles Aug. 27, 2012

Aug. 27, 2012

Aaron Iles added the comment: I've submitted a patch which adds a section to the code module's documentation on overriding console output. It attempts to catalogue when sys.stderr, sys.excepthook and sys.displayhook are used to print console output. ---------- keywords: +patch nosy: +aliles Added file: http://bugs.python.org/file27014/p1346072775.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12403> _______________________________________

1 0

[issue9650] format codes in time.strptime docstrings
by Alexander Belopolsky Aug. 27, 2012

Aug. 27, 2012

Alexander Belopolsky added the comment: I would like to add my +1 to this issue. I suggest adding something like this: """ Commonly used format codes: %Y Year with century as a decimal number. %m Month as a decimal number [01,12]. %d Day of the month as a decimal number [01,31]. %H Hour (24-hour clock) as a decimal number [00,23]. %M Minute as a decimal number [00,59]. %S Second as a decimal number [00,61]. %z Time zone offset from UTC. %a Locale’s abbreviated weekday name. %A Locale’s full weekday name. %b Locale’s abbreviated month name. %B Locale’s full month name. %c Locale’s appropriate date and time representation. Other codes may be available on your platform. See documentation for the C library strftime function. """ This is a subjective selection in a subjective order of importance, so some bikesheding is welcome. My choice was motivated by the assumption that most commonly used are the codes required to form RFC 3339 timestamps. I deliberately omitted deprecated %y code and the %Z code that produces non-standardized TZ names. I can be persuaded to add 12 hour clock codes. ---------- assignee: docs@python -> belopolsky _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9650> _______________________________________

1 0