Mailman 3 February 2020 - docs

[issue13077] Unclear behavior of daemon threads on main thread exit
by etuardu March 9, 2020

March 9, 2020

New submission from etuardu <edonan(a)gmail.com>: The definition of daemon thread in the current documentation reads: «A thread can be flagged as a "daemon thread". The significance of this flag is that the entire Python program exits when only daemon threads are left. [...]» (http://docs.python.org/library/threading.html#thread-objects) I think it's not very clear from this that daemon threads themselves terminate when the program (main thread plus other non-daemon threads) terminates. I think this have to be said more explicitly. I'd propose a change with something like: «A thread can be flagged as a "daemon thread", which means it will get shut down when the overall program terminates. The entire Python program exits when only daemon threads are left.» ---------- assignee: docs@python components: Documentation messages: 144691 nosy: docs@python, etuardu priority: normal severity: normal status: open title: Unclear behavior of daemon threads on main thread exit type: behavior versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13077> _______________________________________

5 7

[issue18269] Clarify which integer is required in os.chmod() exception
by anatoly techtonik March 6, 2020

March 6, 2020

New submission from anatoly techtonik: (<type 'int'>, '0755') (<type 'int'>, '0644') Traceback (most recent call last): File "./tools/bootstrap.py", line 185, in extract_zip os.fchmod(outfile, unixperm) TypeError: an integer is required Here the integer that is required is not `unixperm`, but `outfile`. ---------- assignee: docs@python components: Documentation messages: 191502 nosy: docs@python, techtonik priority: normal severity: normal status: open title: Clarify which integer is required in os.chmod() exception versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3, Python 3.4, Python 3.5 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue18269> _______________________________________

3 8

[issue17231] Mark __del__ not being called in cycles as an impl detail
by Maciej Fijalkowski March 6, 2020

March 6, 2020

New submission from Maciej Fijalkowski: Here: http://docs.python.org/2/reference/datamodel.html, as per python-dev discussion ---------- assignee: docs@python components: Documentation messages: 182364 nosy: docs@python, fijall priority: normal severity: normal status: open title: Mark __del__ not being called in cycles as an impl detail type: behavior _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue17231> _______________________________________

5 5

[issue39530] Documentation about comparisons between numeric types is misleading
by Mark Dickinson March 4, 2020

March 4, 2020

New submission from Mark Dickinson <dickinsm(a)gmail.com>: The documentation[1] for comparisons between mixed types says: > [...] when a binary arithmetic operator has operands of different > numeric types, the operand with the "narrower" type is widened to > that of the other, where integer is narrower than floating point, > which is narrower than complex. Comparisons between numbers of > mixed type use the same rule. That "use the same rule" part of the last sentence is misleading: it suggests that (for example) when an int is compared with a float, the int is first converted to a float, and then the two floats are compared. But that's not what actually happens: instead, the exact values of the int and float are compared. (And it's essential that equality comparisons happen that way, else equality becomes intransitive and dictionaries with numeric keys get very confused as a result.) I suggest dropping the last sentence and adding a new paragraph about comparisons between numbers of mixed type. [1] https://github.com/python/cpython/blob/master/Doc/library/stdtypes.rst#nume… ---------- assignee: docs@python components: Documentation messages: 361234 nosy: docs@python, mark.dickinson priority: normal severity: normal status: open title: Documentation about comparisons between numeric types is misleading versions: Python 3.7, Python 3.8, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue39530> _______________________________________

3 10

[issue36490] Modernize function signature format in Archiving section of shutil doc
by C.A.M. Gerlach March 4, 2020

March 4, 2020

New submission from C.A.M. Gerlach <CAM.Gerlach(a)Gerlach.CAM>: In the process of updating the documentation for another issue, I noticed that unlike the rest of the shutil doc (and the Python docs in general, not to mention those of virtually every Python package), all the functions in the [Archiving operations section](https://docs.python.org/3/library/shutil.html#archiving-operations) uses the old style, difficult to parse nested-bracket notation for the function signatures, rather then the modern style displaying them as they would be expected to appear in Python code, with clearly and explicitly indicated defaults. Therefore, given all bracketed items are keyword arguments with defaults, and there are no cases more complex then the standard linearly-nested brackets, is there a particular reason why this was retained? Otherwise, I can go ahead and submit a PR to update this. ---------- assignee: docs@python components: Documentation messages: 339243 nosy: CAM-Gerlach, docs@python priority: normal severity: normal status: open title: Modernize function signature format in Archiving section of shutil doc versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36490> _______________________________________

4 5

[issue39712] Doc for `-X dev` option should mention PYTHONDEVMODE
by Antoine Pitrou Feb. 29, 2020

Feb. 29, 2020

New submission from Antoine Pitrou <pitrou(a)free.fr>: In the doc for `-X` options (https://docs.python.org/3/using/cmdline.html#id5), when an option can be triggered through an equivalent environment variable, that variable is mentioned. An exception to that is `-X dev`, which can also be triggered by the PYTHONDEVMODE variable, but that isn't mentioned in the CLI doc. Other missing environment variables in the CLI doc are PYTHONFAULTHANDLER and PYTHONTRACEMALLOC. ---------- assignee: docs@python components: Documentation keywords: easy, newcomer friendly messages: 362414 nosy: docs@python, eric.araujo, ezio.melotti, mdk, pitrou, vstinner, willingc priority: normal severity: normal stage: needs patch status: open title: Doc for `-X dev` option should mention PYTHONDEVMODE type: enhancement versions: Python 3.7, Python 3.8, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue39712> _______________________________________

5 8

[issue39379] sys.path[0] is already absolute path
by Ken Sato Feb. 29, 2020

Feb. 29, 2020

New submission from Ken Sato <ksato9700(a)gmail.com>: In the "What’s New In Python 3.9" (Doc/whatsnew/3.9.rst), it says > Python now gets the absolute path of the script filename specified on the command line (ex: python3 script.py): the __file__ attribute of the __main__ module and sys.path[0] become an absolute path, rather than a relative path. However, I believe sys.path[0] is already absolute path since the previous versions. We can probably remove "and sys.path[0]" from the phrase to avoid possible confusions. ---------- assignee: docs@python components: Documentation messages: 360239 nosy: docs@python, ksato9700 priority: normal severity: normal status: open title: sys.path[0] is already absolute path versions: Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue39379> _______________________________________

5 8

[issue39718] TYPE_IGNORE, COLONEQUAL missing from py38 changes in token docs
by Shantanu Feb. 29, 2020

Feb. 29, 2020

New submission from Shantanu <hauntsaninja(a)gmail.com>: Changed in version 3.8 section of https://docs.python.org/3/library/token.html should mention the addition of TYPE_IGNORE and COLONEQUAL ---------- assignee: docs@python components: Documentation messages: 362436 nosy: docs@python, hauntsaninja priority: normal severity: normal status: open title: TYPE_IGNORE, COLONEQUAL missing from py38 changes in token docs _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue39718> _______________________________________

3 6

[issue13790] In str.format an incorrect error message for list, tuple, dict, set
by miss-islington Feb. 28, 2020

Feb. 28, 2020

miss-islington <mariatta.wijaya+miss-islington(a)gmail.com> added the comment: New changeset 445152e0d3ab6e4381aef8d1404c2c17a516070f by Miss Islington (bot) in branch '3.8': bpo-13790: Change 'string' to 'specification' in format doc (GH-18690) https://github.com/python/cpython/commit/445152e0d3ab6e4381aef8d1404c2c17a5… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue13790> _______________________________________

1 0

[issue13790] In str.format an incorrect error message for list, tuple, dict, set
by miss-islington Feb. 28, 2020

Feb. 28, 2020

miss-islington <mariatta.wijaya+miss-islington(a)gmail.com> added the comment: New changeset 5157506e043f75f49caecae1c6afee8517a7bbb0 by Miss Islington (bot) in branch '3.7': bpo-13790: Change 'string' to 'specification' in format doc (GH-18690) https://github.com/python/cpython/commit/5157506e043f75f49caecae1c6afee8517… ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue13790> _______________________________________

1 0