Mailman 3 August 2013 - docs

[issue18870] eval() uses latin-1 to decode str
by STINNER Victor Aug. 28, 2013

Aug. 28, 2013

STINNER Victor added the comment: Where / how do you type the eval() instruction? In IDLE, in the interactive prompt (>>>) or in a script (test.py)? What is your OS and what is your locale encoding? Example: $ python -m platform Linux-3.9.4-200.fc18.x86_64-x86_64-with-fedora-18-Spherical_Cow $ python -c 'import locale; print(locale.getpreferredencoding())' UTF-8 ---------- nosy: +haypo _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18870> _______________________________________

1 0

[issue18870] eval() uses latin-1 to decode str
by Antoine Pitrou Aug. 28, 2013

Aug. 28, 2013

Antoine Pitrou added the comment: > Since the default source encoding in python2 is latin-1 Mmh, really? According to PEP 263: Python will default to ASCII as standard encoding if no other encoding hints are given. And indeed when trying Merlijn's code in a .py file rather than an eval() call, I get: SyntaxError: Non-ASCII character '\xc3' in file tcc.py on line 1, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details ---------- components: +Interpreter Core -Documentation nosy: +benjamin.peterson, pitrou type: -> behavior _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18870> _______________________________________

1 0

[issue18870] eval() uses latin-1 to decode str
by R. David Murray Aug. 28, 2013

Aug. 28, 2013

R. David Murray added the comment: I don't think it is even "won't fix". Your "workarounds" are just the way you need to feed non-latin1 text into Python2. Since the default source encoding in python2 is latin-1, and that is documented, I'm not sure what additional documentation you want? ---------- assignee: -> docs@python components: +Documentation nosy: +docs@python, r.david.murray _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18870> _______________________________________

1 0

[issue17902] Document that _elementtree C API cannot use custom TreeBuilder for iterparse or IncrementalParser
by Aaron Oakley Aug. 26, 2013

Aug. 26, 2013

New submission from Aaron Oakley: It would really help to document that the C API can only use the default xml.etree.ElementTree.TreeBuilder for targets with iterparse (and by extension, IncrementalParser). I got a nice surprise about that when I went from 3.2 to 3.3 and started getting "TypeError: event handling only supported for ElementTree.TreeBuilder targets". I included a patch to add notes to iterparse and IncrementalParser, but I'm not sure what to refer to the C module as since xml.etree.cElementTree is deprecated. ---------- assignee: docs@python components: Documentation, XML files: elementtree.rst-340a0.patch keywords: patch messages: 188329 nosy: Aaron.Oakley, docs@python priority: normal severity: normal status: open title: Document that _elementtree C API cannot use custom TreeBuilder for iterparse or IncrementalParser type: behavior versions: Python 3.4 Added file: http://bugs.python.org/file30119/elementtree.rst-340a0.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17902> _______________________________________

4 8

[issue1944] Documentation for PyUnicode_AsString (et al.) missing.
by Martin Panter Aug. 26, 2013

Aug. 26, 2013

Changes by Martin Panter <vadmium+py(a)gmail.com>: ---------- nosy: +vadmium _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue1944> _______________________________________

1 0

[issue18839] Wrong sentence in sys.exit.__doc__
by Marco Buttu Aug. 26, 2013

Aug. 26, 2013

New submission from Marco Buttu: Python 3.3:: >>> import sys >>> print(sys.exit.__doc__) exit([status]) Exit the interpreter by raising SystemExit(status). If the status is omitted or None, it defaults to zero (i.e., success). If the status is numeric, it will be used as the system exit status. If it is another kind of object, it will be printed and the system exit status will be one (i.e., failure). The sentence "If the status is numeric, it will be used as the system exit status." is wrong:: >>> sys.exit(3.33) 3.33 $ echo $? 1 It should be "If the status is an *integer*, it will be used as the system exit status.", as specified in the SystemExit `doc`. .. doc: http://docs.python.org/3/library/exceptions.html#SystemExit ---------- assignee: docs@python components: Documentation messages: 196195 nosy: docs@python, marco.buttu priority: normal severity: normal status: open title: Wrong sentence in sys.exit.__doc__ type: behavior _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18839> _______________________________________

3 2

[issue18803] Fix more typos in .py files
by Févry Thibault Aug. 25, 2013

Aug. 25, 2013

New submission from Févry Thibault: Just like issue 18741 and 18705. It also fixes one typo in a C file. ---------- assignee: docs@python components: Documentation files: more_typos.diff keywords: patch messages: 195823 nosy: docs@python, iwontbecreative priority: normal severity: normal status: open title: Fix more typos in .py files type: enhancement versions: Python 3.4 Added file: http://bugs.python.org/file31411/more_typos.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18803> _______________________________________

4 5

[issue14191] argparse doesn't allow optionals within positionals
by paul j3 Aug. 24, 2013

Aug. 24, 2013

Changes by paul j3 <ajipanca(a)gmail.com>: Removed file: http://bugs.python.org/file29880/mixed.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14191> _______________________________________

1 0

[issue14191] argparse doesn't allow optionals within positionals
by paul j3 Aug. 24, 2013

Aug. 24, 2013

Changes by paul j3 <ajipanca(a)gmail.com>: Added file: http://bugs.python.org/file29880/mixed.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14191> _______________________________________

1 0

[issue14191] argparse doesn't allow optionals within positionals
by paul j3 Aug. 24, 2013

Aug. 24, 2013

paul j3 added the comment: Above in http://bugs.python.org/issue14191#msg187051 I proposed a patch that is quite close to bethard's patch in http://bugs.python.org/issue15112#msg166173 Both modify the same place, doing the same (pop items off arg_counts). The logic is a little different. I'd have to look at them more carefully to see whether one is more robust. Thanks for linking that issue. The main issue here is different, allowing for complete intermixing of optionals and positionals. Over at 15112 the issue is intermixing of optionals and 'whole' positionals. My 187051 patch belongs over there. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue14191> _______________________________________

1 0