Mailman 3 February 2020 - docs

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

Feb. 28, 2020

Change by miss-islington <mariatta.wijaya+miss-islington(a)gmail.com>: ---------- pull_requests: +18054 pull_request: https://github.com/python/cpython/pull/18693 _______________________________________ 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

Change by miss-islington <mariatta.wijaya+miss-islington(a)gmail.com>: ---------- nosy: +miss-islington nosy_count: 7.0 -> 8.0 pull_requests: +18052 pull_request: https://github.com/python/cpython/pull/18692 _______________________________________ 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 Terry J. Reedy Feb. 28, 2020

Feb. 28, 2020

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: New changeset 916895f93905f8b8dad677cceff501833f5a633a by Terry Jan Reedy in branch 'master': bpo-13790: Change 'string' to 'specification' in format doc (GH-18690) https://github.com/python/cpython/commit/916895f93905f8b8dad677cceff501833f… ---------- _______________________________________ 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 Terry J. Reedy Feb. 28, 2020

Feb. 28, 2020

Terry J. Reedy <tjreedy(a)udel.edu> added the comment: PR-18690 makes the approved change of 'string' to 'specification'. After merging, I will re-review the other changes in i13790b.diff and possibly make another PR for review. ---------- versions: +Python 3.9 -Python 2.7, Python 3.6 _______________________________________ 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 Terry J. Reedy Feb. 28, 2020

Feb. 28, 2020

Change by Terry J. Reedy <tjreedy(a)udel.edu>: ---------- pull_requests: +18049 pull_request: https://github.com/python/cpython/pull/18690 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue13790> _______________________________________

1 0

[issue8824] Improve documentation of exec
by Terry J. Reedy Feb. 28, 2020

Feb. 28, 2020

New submission from Terry J. Reedy <tjreedy(a)udel.edu>: This doc improvement suggestion is inspired by #991196 (and subsequent duplicates) and the current discussion on py-dev in the thread 'variable name resolution in exec is incorrect' (which is not a correct claim). I believe there is consensus that the doc for exec needs improving. My suggestion (which others may amend) is that the following paragraph (from the 3.x builtin functions exec entry) "In all cases, if the optional parts are omitted, the code is executed in the current scope. If only globals is provided, it must be a dictionary, which will be used for both the global and the local variables. If globals and locals are given, they are used for the global and local variables, respectively. If provided, locals can be any mapping object." have these two sentences added: "If only globals is provided or if onedict is provided as both globals and locals, the code is executed in a new top-level scope. If different objects are given as globals and locals, the code is executed as if it were in a class statement in a new top-level scope." ---------- assignee: docs@python components: Documentation messages: 106552 nosy: docs@python, tjreedy priority: normal severity: normal status: open title: Improve documentation of exec versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue8824> _______________________________________

6 19

Addressed to Guido van Rossum
by Bob Xu Feb. 28, 2020

Feb. 28, 2020

Dear Guido van Rossum and the team, In your book, Python Tutorial Release 3.7.0, on page 69, you said "In C++ terminology, normally class members (including the data members) are public (except see below Private Variables)". Is this incorrect? I love your tutorial, and am grateful to your teaching. Just one question above. Thanks, Bob Xu

1 0

[issue39730] Licence (license) for Python 3.8.1 is missing
by Mark Fernandes Feb. 27, 2020

Feb. 27, 2020

New submission from Mark Fernandes <mark.j.fernandes(a)gmail.com>: At https://docs.python.org/3/license.html , the licence agreement for Python 3.8.2rc2 appears, however, I can't see the agreement for 3.8.1. It appears to be missing. Likewise, other licences for various version numbers appear to be missing. Also, it would be really helpful if you said one or more of the following: - that the licence only concerns: + copying, distribution, etc. + granting you extra copyright freedoms to those you already have under applicable law. - that there are no restrictions imposed on you by the licence, for the simple ordinary use of the software (that is other than copying, etc.) for x, y, z purposes. - that if you comply with the GPLv3 licence with respect to the software, you also meet the compliance requirements under the Python licence, and so you can treat the software as though it is GPLv3 software however, if you so treat the software, the software is still nonetheless licensed to you under the Python licence and NOT the GPL licence. ---------- assignee: docs@python components: Documentation messages: 362500 nosy: Mark Fernandes, docs@python priority: normal severity: normal status: open title: Licence (license) for Python 3.8.1 is missing versions: Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue39730> _______________________________________

3 2

[issue15474] Differentiate decorator and decorator factory in docs
by Éric Araujo Feb. 27, 2020

Feb. 27, 2020

New submission from Éric Araujo <merwok(a)netwok.org>: Some of the confusion encountered when writing decorators arise from the difference between a decorator (@something) and a decorator factory (@something(args)). It would help to adopt this clearer terminology in our docs: a decorator takes the decorated function as argument and does its business, a decorator factory takes some arguments and returns a decorator which wraps the decorated function. (I think it was Nick who suggested this in a recent-ish mailing list thread.) ---------- assignee: docs@python components: Documentation messages: 166600 nosy: docs@python, eric.araujo, ncoghlan priority: normal severity: normal status: open title: Differentiate decorator and decorator factory in docs versions: Python 2.7, Python 3.2, Python 3.3 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue15474> _______________________________________

8 14

[issue23164] "pydoc filter" documentation restrictive
by Eric O. LEBIGOT Feb. 26, 2020

Feb. 26, 2020

New submission from Eric O. LEBIGOT: The pydoc documentation for filter reads: filter(function or None, sequence) -> list, tuple, or string Return those items of sequence for which function(item) is true. If function is None, return the items that are true. If sequence is a tuple or string, return the same type, else return a list. It would be nicer to know (e.g. when offline and with no local access to the HTML documentation) that filter() can actually be used more generally with an iterable: filter(function or None, **iterable**) -> list, tuple, or string Return those items of **iterable** for which… ---------- assignee: docs@python components: Documentation messages: 233416 nosy: docs@python, lebigot priority: normal severity: normal status: open title: "pydoc filter" documentation restrictive type: enhancement versions: Python 2.7 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue23164> _______________________________________

2 1