Mailman 3 December 2017 - docs

[issue11023] pep 227 missing text
by Alan Isaac 25 Jan '18

25 Jan '18

New submission from Alan Isaac <alan.isaac(a)gmail.com>: In PEP 227 missing text is marked with XXX. Most of this is just calls for examples and elaboration. However under the Implementation section XXX marks a substantive question about the documentation. Fixing this may be low priority, but a tracker search suggested it is currently not even being tracked ... ---------- assignee: docs@python components: Documentation messages: 127184 nosy: aisaac, docs@python priority: normal severity: normal status: open title: pep 227 missing text type: feature request _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11023> _______________________________________

4 3

[issue12706] timeout sentinel in ftplib and poplib
by Senthil Kumaran 24 Jan '18

24 Jan '18

New submission from Senthil Kumaran <senthil(a)uthcode.com>: - ftplib and poplib, has them as timeout=None, while they default to socket._GLOBAL_DEFAULT_TIMEOUT object. This is wrong; someone may pass None thinking it will trigger the default behaviour, and have nasty surprises. ---------- assignee: docs@python messages: 141740 nosy: docs@python, orsenthil priority: normal severity: normal stage: needs patch status: open title: timeout sentinel in ftplib and poplib type: behavior versions: Python 2.7, Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue12706> _______________________________________

5 7

[issue17799] settrace docs are wrong about "c_call" events
by Ned Batchelder 24 Jan '18

24 Jan '18

New submission from Ned Batchelder: Looking into this Stack Overflow question: http://stackoverflow.com/questions/16115027/pythons-sys-settrace-wont-creat… Reading the code in c_eval.c and friends, it looks like "c_call" events are never passed to the trace function, only to the profile function. The docs are wrong and should be fixed. The setprofile docs simply point to settrace for details, so the text needs to accommodate both functions' needs. ---------- assignee: docs@python components: Documentation messages: 187406 nosy: docs@python, nedbat priority: low severity: normal status: open title: settrace docs are wrong about "c_call" events versions: Python 2.7, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17799> _______________________________________

7 15

[issue15221] os.path.is*() may return False if path can't be accessed
by Giampaolo Rodola' 14 Jan '18

14 Jan '18

New submission from Giampaolo Rodola' <g.rodola(a)gmail.com>: It seems a doc fix is the best way to go, in which case I leave this one to a native English speaker: http://mail.python.org/pipermail/python-dev/2012-June/120788.html Alternatively a new 'strict' parameter has been proposed as a workaround: http://mail.python.org/pipermail/python-dev/2012-June/120800.html ---------- assignee: docs@python components: Documentation messages: 164307 nosy: christian.heimes, docs@python, eric.araujo, ezio.melotti, georg.brandl, giampaolo.rodola, ncoghlan priority: normal severity: normal status: open title: os.path.is*() may return False if path can't be accessed versions: Python 2.7, Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15221> _______________________________________

7 9

[issue11260] smtpd-as-a-script feature should be documented and should use argparse
by Xavier Morel 09 Jan '18

09 Jan '18

New submission from Xavier Morel <xavier.morel(a)masklinn.net>: argparse has been merged to the standard library in 3.2, and (tell me if I'm wrong) would therefore be the "best-practices" way to parse command-line arguments. Numerous stdlib modules can be used as scripts, but they tend to have ad-hoc documentation (if they are at all documented) and arguments parsing (using any of the 4 available methods in Python: straight from sys.argv, getopt, optparse and argparse). I picked smtpd as a first shot since it does something useful (SMTP proxy) and has a pretty good (if ad-hoc) command-line documentation. smtpd is currently using getopt for its options parsing and the argument parsing is very cleanly factored: the port only had to replace the implementation of the `parseargs` function (and add and remove some helpers). * The port keeps the existing arguments semantics (including the mandatory host:port syntax for the local and remote specs if overridden) * The port tries to maintain the old error messages, but due to the way argparse works (or the way I used it for the specs) the parity is not perfect when providing incorrect specs * The CLI help uses argparse's formatting, and the documentation for the local and remote specs was set on these arguments rather than as an epilog. The version string was also removed from the help screen * Because they are set by argparse's arguments validation, the status codes on incorrect arguments are slightly different: - running smtpd.py as a regular user without the `--nosetuid` flag still exits with status 1 - providing incorrect spec formats (missing or non-int port) or providing too many positional arguments (3 or more) now exits with status 2 (formerly 1) ---------- assignee: docs@python components: Documentation, Library (Lib) files: smtpd-to-argparse.diff keywords: patch messages: 128917 nosy: barry, docs@python, xmorel priority: normal severity: normal status: open title: smtpd-as-a-script feature should be documented and should use argparse versions: Python 3.3 Added file: http://bugs.python.org/file20812/smtpd-to-argparse.diff _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue11260> _______________________________________

8 18

Python 3.5.2 文档无法下载
by 邹乐 05 Jan '18

05 Jan '18

Hello! I am a beginner for Python，I need the Python Document very much. But the Python 3.5.2 Document Chinese Version can’t download from http://python.usyiyi.cn/translate/python_352/download.html . It’s inconvenient to me for English version.If you could give me the Chinese version.I will really tankfull.. GOOD NIGHT

2 1

About docs
by Winter Is Coming 05 Jan '18

05 Jan '18

When will Chinese documents appear?

2 1

Bug in python tutorial
by Rian van Kampen 05 Jan '18

05 Jan '18

Hi, Im trying to learn python and i can not get the example of 4.1. If statements to work. Every time i fill out x and the first if statement i go to the elif statement. As i put in the colon and hit enter to go to the next line to write the print it executes the lines and gives me a syntax error. The elif statement doesnt come on the same level als the first if statement. I cant find the answer online so could you please help me out? And correct the example of 4.1.? Kind regards, Rian

2 2

[issue32211] Document the bug in re.findall() and re.finditer() in 2.7 and 3.6
by Serhiy Storchaka 04 Jan '18

04 Jan '18

New submission from Serhiy Storchaka <storchaka+cpython(a)gmail.com>: >>> re.findall(r'^|\w+', 'two words') ['', 'wo', 'words'] Seems the current behavior was documented incorrectly in issue732120. It will be fixed in 3.7 (see issue1647489, issue25054), but I hesitate to backport the fix to 3.6 and 2.7 because this can break the user code. For example: In Python 3.6: >>> list(re.finditer(r'(?m)^\s*?$', 'foo\n\n\nbar')) [<_sre.SRE_Match object; span=(4, 4), match=''>, <_sre.SRE_Match object; span=(5, 5), match=''>] In Python 3.7: >>> list(re.finditer(r'(?m)^\s*?$', 'foo\n\n\nbar')) [<re.Match object; span=(4, 4), match=''>, <re.Match object; span=(4, 5), match='\n'>, <re.Match object; span=(5, 5), match=''>] (This is a real pattern used in the docstring module, but with re.sub()). The proposed PR documents the current weird behavior in 2.7 and 3.6. ---------- assignee: docs@python components: Documentation, Regular Expressions messages: 307546 nosy: docs@python, ezio.melotti, mrabarnett, rhettinger, serhiy.storchaka priority: normal severity: normal status: open title: Document the bug in re.findall() and re.finditer() in 2.7 and 3.6 type: enhancement versions: Python 2.7, Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue32211> _______________________________________

1 5

[issue32452] Brackets and Parentheses used in an ambiguous way
by kandhan 02 Jan '18

02 Jan '18

New submission from kandhan <kandhan.kuhan(a)gmail.com>: https://docs.python.org/3/tutorial/classes.html 9.10. Generator Expressions Some simple generators can be coded succinctly as expressions using a syntax similar to list comprehensions but with "parentheses instead of brackets" Since parentheses comes under brackets, brackets could be changed to "Square Brackets" ---------- assignee: docs@python components: Documentation messages: 309216 nosy: docs@python, kandhan priority: normal severity: normal status: open title: Brackets and Parentheses used in an ambiguous way type: enhancement versions: Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue32452> _______________________________________

6 14