Mailman 3 November 2010 - docs

[issue10433] Document unique behavior of 'getgroups' on OSX
by R. David Murray Nov. 16, 2010

Nov. 16, 2010

Changes by R. David Murray <rdmurray(a)bitdance.com>: ---------- nosy: +ned.deily, ronaldoussoren _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10433> _______________________________________

1 0

[issue10433] Document unique behavior of 'getgroups' on OSX
by Alexander Belopolsky Nov. 16, 2010

Nov. 16, 2010

Changes by Alexander Belopolsky <belopolsky(a)users.sourceforge.net>: ---------- assignee: -> docs@python components: +Documentation, Macintosh nosy: +docs@python versions: +Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10433> _______________________________________

1 0

link is broken in http://docs.python.org/py3k/library/xml.etree.elementtree.html
by "François Burtin, Akis" Nov. 16, 2010

Nov. 16, 2010

http://effbot.org/zone/element-index.htm is no more hosted by WebFaction ? : Site not configured (this link is in v2.7 doc too)

2 1

regular expression documentation bug
by Alexandros Marinos Nov. 16, 2010

Nov. 16, 2010

In the page http://docs.python.org/library/re.html, section 7.2.1, it says: '$' Matches the end of the string [...] foo matches both ‘foo’ and ‘foobar’, while the regular expression foo$ matches only ‘foo’. this last sentence looked odd, so I tried it: print re.match('foo$', 'foobar') output: "None" I think a better example would be something like 'foobarfoo'. Regards, Alexandros

2 1

The result varies from the desired result as per document
by Dosapati, Manikumar Nov. 15, 2010

Nov. 15, 2010

Hi Team, On running the program given in section 4.4, the actual result is varying from expected and displayed result as shown in the tutorial. Please provide inputs regarding this behavior and suggest where I am going wrong. The program is for n in range(2, 10): ... for x in range(2, n): ... if n % x == 0: ... print(n, 'equals', x, '*', n//x) ... break ... else: ... # loop fell through without finding a factor ... print(n, 'is a prime number') The displayed or expected result as per tutorial is 2 is a prime number 3 is a prime number 4 equals 2 * 2 5 is a prime number 6 equals 2 * 3 7 is a prime number 8 equals 2 * 4 9 equals 3 * 3 On running the same program getting the result as shown below >>> for n in range(2,10): for x in range(2,n): if n%x ==0: print(n,'equals',x,'*',n//x) break else: print(n,'is aprime number') 3 is aprime number 4 equals 2 * 2 5 is aprime number 5 is aprime number 5 is aprime number 6 equals 2 * 3 7 is aprime number 7 is aprime number 7 is aprime number 7 is aprime number 7 is aprime number 8 equals 2 * 4 9 is aprime number 9 equals 3 * 3 >>> ________________________________ Information contained and transmitted by this e-mail is confidential and proprietary to Patni Computer Systems Ltd and its affiliates (hitherto referred as Patni Computers) and is intended for use only by the recipient. If you are not the intended recipient , you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or netadmin(a)patni.com. Patni Computers does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of Patni Computers. Patni Computers is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While Patni Computers has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about Patni Computers please visit www.patni.com.

1 0

Re: [docs] Extra list comprehension example
by Alexander Belopolsky Nov. 15, 2010

Nov. 15, 2010

> Ruud Althuizen wrote: > I just read this line from section 5.1.5: "To avoid apprehension when > nesting list comprehensions, read from right to left." I must've read > over that bit the first thousand times. Adding the example > probably makes it more obvious. I agree, this maxim, while appropriate for the tutorial, can be better presented. In the current version, the following paragraph is stuck between a nested list comprehension example and an equivalent nested for loop: """ Special care has to be taken for the nested list comprehension: To avoid apprehension when nesting list comprehensions, read from right to left. """ Other than rather subtle indentation, there is nothing to suggest that "To avoid apprehension ..." is an aphorism and that "apprehension" is not a Python term unknown to user. (The word "apprehension" rhymes well with "comprehension," but may lead to confusion if understood to mean "understanding; grasp." If "apprehension" is taken to mean "arrest," the dictum may or may not be helpful depending on the reader's sense of humor.) I think it would be best to move the maxim either to the paragraph before the "mat" example or to a paragraph after the equivalent for-loop. The text should explain the mnemonic nature of the rule and what "read from right to left" means in the "mat" example. Nested list comprehensions should also be contrasted to list comprehensions with multiple for clauses.

1 0

[issue7186] Document specialness of __doc__, and possibly other "special" attributes
by Ezio Melotti Nov. 15, 2010

Nov. 15, 2010

Changes by Ezio Melotti <ezio.melotti(a)gmail.com>: ---------- nosy: +ezio.melotti _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue7186> _______________________________________

1 0

[issue7186] Document specialness of __doc__, and possibly other "special" attributes
by R. David Murray Nov. 15, 2010

Nov. 15, 2010

R. David Murray <rdmurray(a)bitdance.com> added the comment: No, because that patch doesn't document the special inheritance rules for __doc__ (which are uniquely special even among special methods). Now, exactly where one would want to document those rules, I'm not sure. ---------- nosy: +r.david.murray _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue7186> _______________________________________

1 0

Doc bug: v3.1.2 Library Reference 15.1.5 Files and Directories: os.walk()
by John.Franzini＠bigrock.us Nov. 14, 2010

Nov. 14, 2010

The documentation of os.walk() is missing "Availability:". v3.1.2 Library Reference Section 15.1.5 Files and Directories: os.walk() Thanks.

1 0

9.5.1. Multiple Inheritance
by Julien Poissonnier Nov. 14, 2010

Nov. 14, 2010

Minor error in http://docs.python.org/tutorial/classes.html#multiple-inheritance, 9.5.1. Multiple Inheritance: Last paragraph, first sentence has an extra "one" "(where one at least one of the parent classes can be accessed through multiple paths from the bottommost class)" should be "(where at least one of the parent classes can be accessed through multiple paths from the bottommost class)"

1 0