Mailman 3 January 2011 - docs

[issue11000] Doc: ast.parse parses source, not just expressions
by Terry J. Reedy 24 Jan '11

24 Jan '11

New submission from Terry J. Reedy <tjreedy(a)udel.edu>: "ast.parse(expr, filename='<unknown>', mode='exec') Parse an expression into an AST node. Equivalent to compile(expr, filename, mode, ast.PyCF_ONLY_AST)." but "compile(source, ...) Compile the source into a code or AST object. ... The mode argument specifies what kind of code must be compiled; it can be 'exec' if source consists of a sequence of statements," and indeed, with all three versions, >>> import ast >>> e3=ast.parse('x=1; y=2\nif x: print(y)') >>> o3 = compile(e3,'','exec') >>> exec(o3) 2 >>> print(x,y) (1, 2) Attached patch (untested) changes doc and doc string. Inquiry: I suspect that the filename is *not* attached to the ast. (In any case, it must be explicitly supplied to a subsequent compile() call.) If so, it is a useless parameter and the api and doc should be parse(source, mode) ... Equivalent to compile(source, '<unknown>', ... If so, and failing such a change, should the doc warn people to not bother supplying a filename arg? I also wonder whether the mode arg has any effect on the ast. If not, same question. ---------- assignee: docs@python components: Documentation files: zast.diff keywords: patch messages: 126952 nosy: docs@python, georg.brandl, terry.reedy priority: normal severity: normal status: open title: Doc: ast.parse parses source, not just expressions versions: Python 2.7, Python 3.1, Python 3.2 Added file: http://bugs.python.org/file20506/zast.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11000> _______________________________________

2 2

[issue10960] os.stat() does not mention that it follow symlinks by default
by Марк Коренберг 24 Jan '11

24 Jan '11

New submission from Марк Коренберг <socketpair(a)gmail.com>: Documentation should say about 'following symlink' in this function. Documentation should advice to use os.lstat() in case when it needed. ---------- assignee: docs@python components: Documentation messages: 126631 nosy: docs@python, mmarkk priority: normal severity: normal status: open title: os.stat() does not mention that it follow symlinks by default type: behavior _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10960> _______________________________________

4 7

string.Formatter.format
by Wolfgang Rohdewald 24 Jan '11

24 Jan '11

says *kwargs, shouldn't that be **kwargs? http://docs.python.org/dev/library/string.html#string.Formatter -- Wolfgang

2 1

[issue10996] Typo in What's New in 3.2
by Daniel Urban 24 Jan '11

24 Jan '11

New submission from Daniel Urban <urban.dani+py(a)gmail.com>: In http://docs.python.org/dev/py3k/whatsnew/3.2.html#abc the example has two typos: farenheit -> fahrenheit celsium -> celsius ---------- assignee: docs@python components: Documentation messages: 126938 nosy: docs@python, durban priority: normal severity: normal status: open title: Typo in What's New in 3.2 type: behavior versions: Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10996> _______________________________________

2 2

[issue10976] json.loads() throws TypeError on bytes object
by hhas 22 Jan '11

22 Jan '11

hhas <hhas(a)users.sourceforge.net> added the comment: Doc fix works for me. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10976> _______________________________________

1 0

[issue9723] pipes.quote() needs to be documented
by Brandon Craig Rhodes 22 Jan '11

22 Jan '11

New submission from Brandon Craig Rhodes <brandon(a)rhodesmill.org>: The only way to safely build shell command lines from inside of Python — which is necessary when sending commands across SSH, since that behaves like os.system() rather than like subprocess.call() — is to use the wonderful pipes.call() method to turn possibly-dangerous arguments, like filenames that might have spaces, special characters, and embedded "rm -r" calls, into perfectly quoted strings for an "sh"-like shell (say, bash or zsh). This call is already recommended on mailing lists, blog posts, and Stack Overflow — and since it doesn't start with a "_", I think its public use is fair game. But the "pipes" documentation itself doesn't officially mention or support it. I think it should be added to the Standard Library documentation for "pipes". So. Yeah. ---------- assignee: docs@python components: Documentation messages: 115263 nosy: brandon-rhodes, docs@python priority: normal severity: normal status: open title: pipes.quote() needs to be documented type: feature request versions: Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue9723> _______________________________________

4 6

[issue10957] Python FAQ grammar error
by Jerry Seutter 21 Jan '11

21 Jan '11

New submission from Jerry Seutter <jseutter(a)gmail.com>: Section 4.1 of the Python FAQ (http://www.python.org/dev/faq/) contains a grammar error: The sentence I am referring to says: "If you are developing on OS X for Python 2.x and will not be working with the OS X-specific modules from the standard library, then consider using the --without-toolbox-glue flag to faster compilation time." How about instead: "If you are developing on OS X for Python 2.x and will not be working with the OS X-specific modules from the standard library, then consider using the --without-toolbox-glue flag for a faster compile." (Note: Taken from the FAQ as of Jan 20, 2011) ---------- assignee: docs@python components: Documentation keywords: easy messages: 126626 nosy: docs@python, jerry.seutter priority: normal severity: normal status: open title: Python FAQ grammar error versions: Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10957> _______________________________________

4 5

[issue10976] json.loads() throws TypeError on bytes object
by Antoine Pitrou 21 Jan '11

21 Jan '11

Antoine Pitrou <pitrou(a)free.fr> added the comment: I've committed a doc fix in r88137. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10976> _______________________________________

1 0

[issue10976] json.loads() throws TypeError on bytes object
by Éric Araujo 21 Jan '11

21 Jan '11

Éric Araujo <merwok(a)netwok.org> added the comment: Georg: Is it still time to deprecate the encoding parameter in 3.2? ---------- nosy: +eric.araujo, georg.brandl _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10976> _______________________________________

1 0

[issue10976] json.loads() throws TypeError on bytes object
by Antoine Pitrou 21 Jan '11

21 Jan '11

Antoine Pitrou <pitrou(a)free.fr> added the comment: Indeed, the documentation (and function docstring) needs fixing instead. It's a pity we didn't remove the useless `encoding` parameter. ---------- assignee: -> docs@python components: +Documentation -Library (Lib) nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue10976> _______________________________________

1 0