Mailman 3 November 2010 - docs

[issue10589] I/O ABC docs should specify which methods have implementations
by Antoine Pitrou 30 Nov '10

30 Nov '10

Antoine Pitrou <pitrou(a)free.fr> added the comment: What does "unsupported" mean? "Abstract" would look more exact. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10589> _______________________________________

1 0

[issue10589] I/O ABC docs should specify which methods have implementations
by Fred L. Drake, Jr. 30 Nov '10

30 Nov '10

Changes by Fred L. Drake, Jr. <fdrake(a)acm.org>: ---------- nosy: +docs@python, fdrake _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10589> _______________________________________

1 0

Documentation bug
by Seemant Kulleen 30 Nov '10

30 Nov '10

Hi, The page is: http://docs.python.org/library/pickle.html The diff I propose: --- pickle.txt.orig 2010-11-30 09:30:47.835228859 -0500 +++ pickle.txt 2010-11-30 09:31:22.993228853 -0500 @@ -53,7 +53,7 @@ objects. :mod:`marshal` exists primarily to support Python's :file:`.pyc` files. -The :mod:`pickle` module differs from :mod:`marshal` several significant ways: +The :mod:`pickle` module differs from :mod:`marshal` in several significant ways: * The :mod:`pickle` module keeps track of the objects it has already serialized, so that later references to the same object won't be serialized again. Thanks! Seemant

2 1

[issue10584] Bad links in doc of zipfile.open
by Éric Araujo 30 Nov '10

30 Nov '10

New submission from Éric Araujo <merwok(a)netwok.org>: There is this note in the doc of zipfile.open: “The file-like object [ZipExtFile, internal class] is read-only and provides the following methods: read(), readline(), readlines(), __iter__(), __next__().” The :meth: construct gives interesting results here: link to zipfile.ZipFile.read (wrong), link to readline module (what?), no link, link to object.__iter__ (not bad), no link. ---------- assignee: docs@python components: Documentation messages: 122871 nosy: docs@python, eric.araujo priority: normal severity: normal status: open title: Bad links in doc of zipfile.open versions: Python 2.7, Python 3.1, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10584> _______________________________________

2 1

[issue5088] optparse: inconsistent default value for append actions
by Éric Araujo 30 Nov '10

30 Nov '10

Changes by Éric Araujo <merwok(a)netwok.org>: ---------- status: open -> pending _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue5088> _______________________________________

1 0

Re: [docs] (take 2) Python 3.1.2 xml.sax doc error, or bug, or error by the operator...
by Éric Araujo 29 Nov '10

29 Nov '10

Le 29/11/2010 19:57, Ryan, Thomas a écrit : > Thank you. > I will check that out. > The documentation, "string", and the implementation, bytes, may be out of synch. Yes, http://docs.python.org/dev/library/xml.sax is not clear on bytes vs. characters. Please open a documentation bug at bugs.python.org. Regards

1 0

[issue10579] Is ``o[key]`` equivalent to PyMapping_HasKeyString?
by INADA Naoki 29 Nov '10

29 Nov '10

New submission from INADA Naoki <songofacandy(a)gmail.com>: http://docs.python.org/c-api/mapping.html#PyMapping_HasKeyString and http://docs.python.org/c-api/mapping.html#PyMapping_HasKey says: > This is equivalent to ``o[key]`` I think it should be ``key in o``. ---------- assignee: docs@python components: Documentation messages: 122824 nosy: docs@python, naoki priority: normal severity: normal status: open title: Is ``o[key]`` equivalent to PyMapping_HasKeyString? versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10579> _______________________________________

1 1

[issue10559] NameError in tutorial/interpreter
by Éric Araujo 29 Nov '10

29 Nov '10

Éric Araujo <merwok(a)netwok.org> added the comment: What about: “You need to execute ``import sys`` before you can use ``sys.argv``.” ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10559> _______________________________________

1 0

[issue10559] NameError in tutorial/interpreter
by Senthil Kumaran 29 Nov '10

29 Nov '10

Senthil Kumaran <orsenthil(a)gmail.com> added the comment: On Sun, Nov 28, 2010 at 05:48:20AM +0000, Éric Araujo wrote: > I’m not committing directly because I’d like feedback: Is the > wording okay for the beginning of the tutorial? It seems fine and useful. Please go ahead. ---------- nosy: +orsenthil _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10559> _______________________________________

1 0

[issue10559] NameError in tutorial/interpreter
by Ezio Melotti 28 Nov '10

28 Nov '10

Ezio Melotti <ezio.melotti(a)gmail.com> added the comment: What about "In order to use ``sys.argv`` you have to import the :mod:`sys` module doing ``import sys``.". "reference" sounds weird to me, and imho saying "import the module" is ok even if imports have not been introduced yet. If the user doesn't understand what "importing a module" means he can just execute the command as is. ---------- nosy: +ezio.melotti _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10559> _______________________________________

1 0