Mailman 3 April 2019 - docs

[issue36416] bytes.rpartition bug in online documentation
by PEW's Corner April 11, 2019

April 11, 2019

New submission from PEW's Corner <pewscorner(a)gmail.com>: The online Python 3 documentation for bytes.rpartition and bytearray.rpartition (https://docs.python.org/3/library/stdtypes.html#bytes.rpartition) incorrectly states: "If the separator is not found, return a 3-tuple containing a copy of the original sequence, followed by two empty bytes or bytearray objects." This seems to have been copied without modification from bytes.partition where the statement is correct. The statement for rpartition should be: "If the separator is not found, return a 3-tuple containing two empty bytes or bytearray objects, followed by a copy of the original sequence." ---------- assignee: docs@python components: Documentation messages: 338734 nosy: docs@python, pewscorner priority: normal severity: normal status: open title: bytes.rpartition bug in online documentation type: behavior versions: Python 3.7 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36416> _______________________________________

5 9

[issue13282] the table of contents in epub file is too long
by wrobell April 11, 2019

April 11, 2019

New submission from wrobell <wrobell(a)pld-linux.org>: the table of contents in python documentation epub file is very very long. it takes several long minutes to jump from first page to a part containing language reference toc. imho it would be great if first page of epub file contained pointers to tutorial, lang ref, mod ref without detailed table of contents as it is at docs.python.org. ---------- assignee: docs@python components: Documentation messages: 146548 nosy: docs@python, wrobell priority: normal severity: normal status: open title: the table of contents in epub file is too long versions: Python 2.7, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue13282> _______________________________________

4 4

[issue33722] Document builtins in mock_open
by Jay Crotts April 11, 2019

April 11, 2019

New submission from Jay Crotts <crotts.jay(a)gmail.com>: The examples on using mock_open only include instances where objects are mocked in the REPL, so '__main__'.open is replaced. Commonly objects are mocked for use in other test modules, so builtins.open would be used instead. A note about this in the documentation would be useful not familiar with python internals. I'm happy to do a PR for it. ---------- assignee: docs@python components: Documentation messages: 318337 nosy: docs@python, jcrotts priority: normal severity: normal status: open title: Document builtins in mock_open type: enhancement versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue33722> _______________________________________

3 8

[issue30274] Make importlib.abc.ExtensionFileLoader.__init__() documentation match code
by Brett Cannon April 10, 2019

April 10, 2019

New submission from Brett Cannon: https://docs.python.org/3/library/importlib.html#importlib.machinery.Extens… says "fullname, path" for __init__(), but https://github.com/python/cpython/blob/647c3d381e67490e82cdbbe6c96e46d5e162… says "name, path". While I would much rather change the parameter name to match the rest of the module, I don't think I'm comfortable with the backwards-compatibility breakage over just a single parameter name (although chances are no one will notice in either direction as everyone probably passes by position). ---------- assignee: docs@python components: Documentation messages: 293022 nosy: brett.cannon, docs@python priority: normal severity: normal stage: needs patch status: open title: Make importlib.abc.ExtensionFileLoader.__init__() documentation match code _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue30274> _______________________________________

3 5

[issue28626] Tutorial: rearrange discussion of output formatting to encourage f-strings
by A.M. Kuchling April 10, 2019

April 10, 2019

New submission from A.M. Kuchling: The 'output formatting' section of the tutorial talks a lot about manual formatting with things like .rjust() and .zfill(), with only a passing reference to 3.6's new f-strings. The attached patch doesn't drop all of the old material, but it does rearrange the topics into a more modern order: f-strings first, featuring the discussion of formatting specifiers; then calling .format(); finally manual formatting with .ljust(). Open question: ---------- assignee: docs@python components: Documentation files: tutorial-patch.txt keywords: needs review, patch messages: 280153 nosy: akuchling, docs@python priority: normal severity: normal stage: patch review status: open title: Tutorial: rearrange discussion of output formatting to encourage f-strings type: enhancement versions: Python 3.6 Added file: http://bugs.python.org/file45372/tutorial-patch.txt _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue28626> _______________________________________

4 8

[issue29284] Include thread_name_prefix in the concurrent.futures.ThreadPoolExecutor example 17.4.2.1
by John Taylor April 10, 2019

April 10, 2019

New submission from John Taylor: Please include how to use the thread_name_prefix method argument (new to Python 3.6) in the example: 17.4.2.1. ThreadPoolExecutor Example ---------- assignee: docs@python components: Documentation messages: 285572 nosy: docs@python, jftuga priority: normal severity: normal status: open title: Include thread_name_prefix in the concurrent.futures.ThreadPoolExecutor example 17.4.2.1 type: enhancement versions: Python 3.6 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue29284> _______________________________________

3 6

Bug on the site page - descriptor
by Иван Благополучный April 10, 2019

April 10, 2019

Hello! I was found next issue: https://docs.python.org/3.3/howto/descriptor.html On this page, in the text block: For objects, the machinery is in object.__getattribute__() which transforms b.x into type(b).__dict__['x'].__get__(b, type(b)). The implementation works through a precedence chain that gives data descriptors priority over instance variables, instance variables priority over non-data descriptors, and assigns lowest priority to __getattr__() if provided. The full C implementation can be found in PyObject_GenericGetAttr() in Objects/object.c. There not found page while refereed by click on Onject.c http://svn.python.org/view/python/trunk/Objects/object.c?view=markup [image: image.png]

2 1

[issue34172] multiprocessing.Pool and ThreadPool leak resources after being deleted
by Vy Nguyen April 9, 2019

April 9, 2019

Change by Vy Nguyen <thaovy231011(a)gmail.com>: ---------- nosy: +Vy Nguyen _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue34172> _______________________________________

1 0

[issue30134] BytesWarning is missing from the documents
by KINEBUCHI Tomohiko April 9, 2019

April 9, 2019

New submission from KINEBUCHI Tomohiko: In Python 2.6, BytesWarning was added, but a description of that warning is missing from the document, library/exceptions.rst. ---------- assignee: docs@python components: Documentation messages: 292099 nosy: cocoatomo, docs@python priority: normal severity: normal status: open title: BytesWarning is missing from the documents versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue30134> _______________________________________

4 14

Improvement suggestion to Python docs
by Klaas `Z4us` Van B. V April 9, 2019

April 9, 2019

Dear documentation writers for Python, Better late than never I started to learn Python after some other like Perl, Ruby & C In the beginning of your tutorial <https://docs.python.org/2.7/tutorial/interpreter.html> (2.1) is written: ... usually installed as /usr/local/bin/python on those ... Perhaps better, because more generic if you write something like: *To find out where Python is located type 'which python' ...* [then you may remove a line or two like the one about consulting a guru as well] *BTW * On Snow Leopard 2.6 installed and works great Kind regards | Vriendelijke groeten | Cordiali saluti, Klaas `Z4us` van B V, EFIG <https://nl.linkedin.com/in/klaas-van-buiten-0325b2102>

2 2