Mailman 3 March 2012 - docs

Request for pre-built .CHM on Doc Download page
by Nam Nguyen March 13, 2012

March 13, 2012

Hi, Before 2.7, one can easily find .CHM files in the Documentation download page. When 2.7 come out, the only way to get CHM files is downloading the Windows installers (EXE or MSI), installing it on Windows, and grabbing the CHM files. This is unwieldy. I am on a Mac at work, have a desktop running Linux and Windows at home. In all cases, I usually rely on the CHM file. It is self-packaged, indexable, and easily searchable. There are CHM readers out there that work across different OSes … [View More]

1 0

[issue14257] minor error in glossary wording regarding __hash__
by Chris Rebert March 13, 2012

March 13, 2012

New submission from Chris Rebert <pybugs(a)rebertia.com>: The entry for "dictionary" reads in part: [...] The keys can be any object with __hash__() function and __eq__() methods. [...] __hash__() is a method, not a function (well, it's a "hash function" in the computer science sense, but it's still confusing even if that reading is what was intended; I think delegating the hashing part of the explanation to __hash__()'s docs is fine). Remove the word "function" from said sentence. … [View More]

2 3

str.lstrip(char) takes too many characters
by Byron Freelon March 11, 2012

March 11, 2012

Hi, I have a string trans_11.79_1.78_133392642.sdds if I execute >> test = trans_11.79_1.78_133392642.sdds >> test.lstrip("trans" + "_" + 11.79 + "_" + 1.78 + "_").rstrip(".sdds") I get the result 33392642 a friend verified this problem. Thanks

2 1

Re: [docs] [issue14245] float rounding examples in FAQ are outdated
by John Roth March 10, 2012

March 10, 2012

I keep looking at this issue. What rattles around in my head is the satori I had when I first heard "integers are for things that are counted, floats are for things that are measured." Possibly something to the effect that "the industry standard for floating point is intended for measurements, which are never absolutely precise. Thus floating point, by its nature, will not usually represent factions as precisely as one would like."

1 0

[issue14248] Typo in "What’s New In Python 3.3": "comparaison"
by Jakub Wilk March 10, 2012

March 10, 2012

New submission from Jakub Wilk <jwilk(a)jwilk.net>: Typo in Doc/whatsnew/3.3.rst: "comparaison" -> "comparison". ---------- assignee: docs@python components: Documentation messages: 155347 nosy: docs@python, jwilk priority: normal severity: normal status: open title: Typo in "What’s New In Python 3.3": "comparaison" versions: Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14248> _______________________________________

2 1

[issue14186] Link to PEP 3107 in "def" part of Language Reference
by Chris Rebert March 10, 2012

March 10, 2012

New submission from Chris Rebert <pybugs(a)rebertia.com>: The part of the Language Reference concerning the `def` statement (http://docs.python.org/dev/reference/compound_stmts.htm#function-definitions ) should include a See Also link to PEP 3107 "Function Annotations". ---------- assignee: docs@python components: Documentation messages: 154851 nosy: cvrebert, docs@python priority: normal severity: normal status: open title: Link to PEP 3107 in "def" part of Language Reference versions: … [View More]

3 3

[issue14191] argparse: nargs='*' doesn't get out-of-order positional parameters
by Glenn Linderman March 10, 2012

March 10, 2012

Glenn Linderman <v+python(a)g.nevcal.com> added the comment: Of course, if a "real" solution can only be shipped in 3.3, it may want to use a different API than parse_args to avoid the parameter, parse_intermixed_args, perhaps. But my t18.py uses the name parse_args, but just always does the intermixed parsing, so that is something to be aware of if building on that code at all, for the real solution or for sample code for older versions. ---------- … [View More]

1 0

[issue14191] argparse: nargs='*' doesn't get out-of-order positional parameters
by Glenn Linderman March 10, 2012

March 10, 2012

Glenn Linderman <v+python(a)g.nevcal.com> added the comment: Sad. That means all the documentation of workarounds needs to be written, even figured out in the first place. Steven's code, while being a nice implementation when proper arguments are provided, produces inappropriate errors, because only the positional, or only the optional, parameters are printed when errors occur. So it would probably take a third parser, with all the parameters defined, to exist, to allow easiest … [View More]

1 0

[issue14191] argparse: nargs='*' doesn't get out-of-order positional parameters
by R. David Murray March 9, 2012

March 9, 2012

R. David Murray <rdmurray(a)bitdance.com> added the comment: To answer Glenn's procedural question: no this is not a bug whose fix can be backported. API changes are not allowed in maintenance releases. Doc improvements can be backported, though, so I'm leaving versios alone (alternatively someone could split this into two bugs, one for the doc fixes for older releases, and one for adding the new capability). ---------- assignee: -> docs@python components: +Documentation nosy: +… [View More]

1 0

[issue14201] Documented caching for shared library's __getattr__ and __getitem__ is incorrect
by Erik Johansson March 7, 2012

March 7, 2012

Erik Johansson <erik(a)ejohansson.se> added the comment: Ah, I see. I modified the title to reflect this. Perhaps adding this simple example as well can help people (e.g. me) see it? >>> libc.time == libc.time True >>> libc['time'] == libc['time'] False ---------- title: libc.time != libc['time'] -> Documented caching for shared library's __getattr__ and __getitem__ is incorrect _______________________________________ Python tracker <report(a)bugs.python.org&… [View More]

1 0