Mailman 3 August 2015 - docs

[issue4395] Document auto __ne__ generation; provide a use case for non-trivial __ne__
by Robert Collins 06 Aug '15

06 Aug '15

Robert Collins added the comment: Thanks for the patch; applied to 3.4 and up. ---------- nosy: +rbcollins resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue4395> _______________________________________

1 0

[issue4395] Document auto __ne__ generation; provide a use case for non-trivial __ne__
by Roundup Robot 06 Aug '15

06 Aug '15

Roundup Robot added the comment: New changeset f5069e6e4229 by Robert Collins in branch '3.4': Issue #4395: Better testing and documentation of binary operators. https://hg.python.org/cpython/rev/f5069e6e4229 New changeset b9a0165a3de8 by Robert Collins in branch '3.5': Issue #4395: Better testing and documentation of binary operators. https://hg.python.org/cpython/rev/b9a0165a3de8 New changeset e56893df8e76 by Robert Collins in branch 'default': Issue #4395: Better testing and documentation of binary operators. https://hg.python.org/cpython/rev/e56893df8e76 ---------- nosy: +python-dev _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue4395> _______________________________________

1 0

[issue24531] please document that no code preceding encoding declaration is allowed
by Jakub Wilk 06 Aug '15

06 Aug '15

New submission from Jakub Wilk: If the encoding is declared on the second line, the first line must not contain anything except comments. However, this fact is not documented. The Python Language reference says only that "the encoding declaration must appear on a line of its own"; and PEP 263 says only that "there must not be any Python statement on the line that contains the encoding declaration". For example, Python ignores this encoding declaration: spam = True # encoding=ISO-8859-2 despite the fact that it appears on a line of its own. ---------- assignee: docs@python components: Documentation messages: 245946 nosy: docs@python, jwilk priority: normal severity: normal status: open title: please document that no code preceding encoding declaration is allowed _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24531> _______________________________________

5 5

[issue21279] str.translate documentation incomplete
by bob gailer 06 Aug '15

06 Aug '15

New submission from bob gailer: Documentation for str.translate only mentions a dictionary for the translation table. Actually any iterable can be used, as long as its elements are integer, None or str. Recommend wording: str.translate(translation_table) Return a copy of the s where all characters have been "mapped" through the translation_table - which must be either a dictionary mapping Unicode ordinals (integers) to Unicode ordinals, strings or None, or an iterable. In this case the ord() of each character in s is used as an index into the iterable; the corresponding element of the iterable replaces the character. If ord() of the character exceeds the index range of the iterator, no substitution is made. Example: to shift any of the first 255 ASCII characters to the next: >>> 'Now is the time for all good men'.translate(range(1, 256)) 'Opx!jt!uif!ujnf!gps!bmm!hppe!nfo' COMMENT: I placed mapped in quotes as technically this only applies to dictionaries. Not sure what the best word is. ---------- assignee: docs@python components: Documentation messages: 216630 nosy: bgailer, docs@python priority: normal severity: normal status: open title: str.translate documentation incomplete type: enhancement versions: Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue21279> _______________________________________

11 26

[issue24800] exec docs should note that the no argument form in a local scope is really the two argument form
by R. David Murray 05 Aug '15

05 Aug '15

R. David Murray added the comment: OK, yes, so "a class body at global scope" or something like that :) LOAD_CLASSDEREF is another whole level of complication to the scoping weirdness for classes; see issue 19979 and issue 24129. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24800> _______________________________________

1 0

[issue24800] exec docs should note that the no argument form in a local scope is really the two argument form
by eryksun 05 Aug '15

05 Aug '15

eryksun added the comment: > If exec gets two separate objects as globals and locals, > the code will be executed as if it were embedded in a > class definition. Probably there needs to be more clarification of the compilation context. Class definitions support lexical closures, whereas source code passed to exec is compiled at the time of the call, independent of the lexical context. In the following example, the code objects for both the class body and the comprehension can access the free variable "a". In CPython, the class body references the free variable via the LOAD_CLASSDEREF op, and the comprehension uses the LOAD_DEREF op. def f(): a = 5 class C: print(a) print([a for i in range(5)]) >>> f() 5 [5, 5, 5, 5, 5] >>> dis.dis(f.__code__.co_consts[2]) 3 0 LOAD_NAME 0 (__name__) 3 STORE_NAME 1 (__module__) 6 LOAD_CONST 0 ('f.<locals>.C') 9 STORE_NAME 2 (__qualname__) 4 12 LOAD_NAME 3 (print) 15 LOAD_CLASSDEREF 0 (a) 18 CALL_FUNCTION 1 (1 positional, 0 keyword pair) 21 POP_TOP 5 22 LOAD_NAME 3 (print) 25 LOAD_CLOSURE 0 (a) 28 BUILD_TUPLE 1 31 LOAD_CONST 1 (<code object <listcomp> ...>) 34 LOAD_CONST 2 ('f.<locals>.C.<listcomp>') 37 MAKE_CLOSURE 0 40 LOAD_NAME 4 (range) 43 LOAD_CONST 3 (5) 46 CALL_FUNCTION 1 (1 positional, 0 keyword pair) 49 GET_ITER 50 CALL_FUNCTION 1 (1 positional, 0 keyword pair) 53 CALL_FUNCTION 1 (1 positional, 0 keyword pair) 56 POP_TOP 57 LOAD_CONST 4 (None) 60 RETURN_VALUE >>> dis.dis(f.__code__.co_consts[2].co_consts[1]) 5 0 BUILD_LIST 0 3 LOAD_FAST 0 (.0) >> 6 FOR_ITER 12 (to 21) 9 STORE_FAST 1 (i) 12 LOAD_DEREF 0 (a) 15 LIST_APPEND 2 18 JUMP_ABSOLUTE 6 >> 21 RETURN_VALUE ---------- nosy: +eryksun _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24800> _______________________________________

1 0

[issue24800] exec docs should note that the no argument form in a local scope is really the two argument form
by R. David Murray 05 Aug '15

05 Aug '15

Changes by R. David Murray <rdmurray(a)bitdance.com>: ---------- versions: +Python 3.5, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24800> _______________________________________

1 0

[issue24800] exec docs should note that the no argument form in a local scope is really the two argument form
by R. David Murray 05 Aug '15

05 Aug '15

R. David Murray added the comment: OK, it looks like what the documentation of exec is missing is the fact that calling exec with no arguments in a non-global is equivalent to calling it with *two* arguments. That is, your "exec(script)" statement is equivalent to "exec(script, globals(), locals())". This is implicit but very much *not* explicit in the current documentation, and should be made explicit. To be sure I'm explaining this fully: the documentation of exec says "If exec gets two separate objects as globals and locals, the code will be executed as if it were embedded in a class definition". >>> class Foo: ... a = 10 ... [a for x in range(5)] ... Traceback (most recent call last): File "<stdin>", line 1, in <module> File "<stdin>", line 3, in Foo File "<stdin>", line 3, in <listcomp> NameError: name 'a' is not defined ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python stage: resolved -> needs patch title: Incorrect handling of local variables in comprehensions with exec() -> exec docs should note that the no argument form in a local scope is really the two argument form _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24800> _______________________________________

1 0

[issue24778] mailcap.findmatch: document shell command Injection danger in filename parameter
by Bernd Dietzel 05 Aug '15

05 Aug '15

Bernd Dietzel added the comment: Thanks :-) As you may noticed i now choosed to use a random name made of the chars of "PYTHON" in BIG letters instead of small letters i used before. Thats because i do not want to get in trouble with the little "t" in %t wich is replaced by the subst function too. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24778> _______________________________________

1 0

[issue24778] mailcap.findmatch: document shell command Injection danger in filename parameter
by R. David Murray 05 Aug '15

05 Aug '15

R. David Murray added the comment: Ah, that's a clever idea. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24778> _______________________________________

1 0