Mailman 3 February 2019 - docs

[issue23460] Decimals do not obey ':g' exponential notation formatting rules
by Stefan Krah 11 Feb '19

11 Feb '19

Stefan Krah <stefan(a)bytereef.org> added the comment: Yes, these days PRs are the only way to get anything done. Before GitHub it would have been possible to just commit the small diff directly to master. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue23460> _______________________________________

1 0

[issue23460] Decimals do not obey ':g' exponential notation formatting rules
by Karthikeyan Singaravelan 11 Feb '19

11 Feb '19

Karthikeyan Singaravelan <tir.karthi(a)gmail.com> added the comment: > If contributions are accepted as GitHub pull requests these days, I can do it myself too. GitHub pull requests are accepted. Please see https://devguide.python.org/ . Thanks ---------- nosy: +xtreak _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue23460> _______________________________________

1 0

[issue23460] Decimals do not obey ':g' exponential notation formatting rules
by Stefan Krah 11 Feb '19

11 Feb '19

Stefan Krah <stefan(a)bytereef.org> added the comment: The patch LGTM, but I'm not sure if we need to document __format__(). Personally I probably wouldn't. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue23460> _______________________________________

1 0

[issue23460] Decimals do not obey ':g' exponential notation formatting rules
by Brennan D Baraban 11 Feb '19

11 Feb '19

Brennan D Baraban <375(a)holbertonschool.com> added the comment: What is the status of this issue? I can submit a PR based on Tuomas Suutari's patch. ---------- nosy: +bdbaraban _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue23460> _______________________________________

2 1

[issue24087] Documentation doesn't explain the term "coroutine" (PEP 342)
by Paul Moore 08 Feb '19

08 Feb '19

New submission from Paul Moore: Although the new generator methods introduced in PEP 342 are documented, the term "coroutine" is not defined anywhere. In particular, the fact that Python coroutines work in conjunction with an event loop rather than transferring control directly between each other is not mentioned. ---------- assignee: docs@python components: Documentation files: coroutine_docs.patch keywords: needs review, patch messages: 242286 nosy: docs@python, gvanrossum, paul.moore priority: normal severity: normal stage: patch review status: open title: Documentation doesn't explain the term "coroutine" (PEP 342) type: enhancement versions: Python 3.5 Added file: http://bugs.python.org/file39239/coroutine_docs.patch _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue24087> _______________________________________

3 6

[issue35533] argparse standard error usage for exit / error
by Philip Rowlands 07 Feb '19

07 Feb '19

New submission from Philip Rowlands <pythonbugs(a)dimebar.com>: Because error() mentions standard error and exit() does not, I assumed exit() did not use stderr, but it does. Please mention standard error in the description of exit(). Relevant code at: https://github.com/python/cpython/blob/3.7/Lib/argparse.py#L2482 ---------- assignee: docs@python components: Documentation messages: 332128 nosy: docs@python, philiprowlands priority: normal severity: normal status: open title: argparse standard error usage for exit / error type: enhancement versions: Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35533> _______________________________________

4 4

[issue35929] rtat.net
by Mariatta Wijaya 07 Feb '19

07 Feb '19

New submission from Mariatta Wijaya <mariatta(a)python.org>: Please provide more info about the bug you're reporting. As it is, this looks like spam, so I'm closing it. ---------- assignee: docs@python -> nosy: +Mariatta resolution: -> not a bug stage: -> resolved status: open -> closed type: resource usage -> _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35929> _______________________________________

1 0

[issue35929] rtat.net
by Rohit travels and tours 07 Feb '19

07 Feb '19

Change by Rohit travels and tours <roufique(a)rtat.net>: ---------- assignee: docs@python components: 2to3 (2.x to 3.x conversion tool), Build, Demos and Tools, Distutils, Documentation, Extension Modules, FreeBSD, Library (Lib), SSL, email, macOS nosy: barry, docs@python, dstufft, eric.araujo, koobs, ned.deily, r.david.murray, ronaldoussoren, roufique7 priority: normal severity: normal status: open title: rtat.net type: resource usage versions: Python 3.6, Python 3.7, Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue35929> _______________________________________

1 0

https://docs.python.org/3/tutorial/venv.html
by lyle_z hotmail.com 06 Feb '19

06 Feb '19

Might want to mention that the way to exit a python virtual environment is with the "deactivate" command. https://docs.python.org/3/tutorial/venv.html Lyle

1 0

[issue22474] No explanation of how a task gets destroyed in asyncio 'task' documentation
by R. David Murray 06 Feb '19

06 Feb '19

New submission from R. David Murray: In https://docs.python.org/3/library/asyncio-task.html#task, there is a note about a warning being logged if a pending task is destroyed. The section does not explain or link to an explanation of how a task might get destroyed. Nor does it define pending, but that seems reasonably clear from context (ie: the future has not completed). The example linked to does not show how the pending task got destroyed, it only shows an example of the resulting logging, with not enough information to really understand what the final line of the error message is reporting (is kill_me an asyncio API, or the name of the task, or the future it is wrapping?) ---------- assignee: docs@python components: Documentation messages: 227400 nosy: docs@python, r.david.murray priority: normal severity: normal status: open title: No explanation of how a task gets destroyed in asyncio 'task' documentation type: behavior versions: Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue22474> _______________________________________

5 5