Mailman 3 April 2021 - docs

[issue43700] Replace Zulip badge with Discourse badge in README
by Erlend Egeberg Aasland 02 Apr '21

02 Apr '21

New submission from Erlend Egeberg Aasland <erlend.aasland(a)innova.no>: Suggesting to follow the dev guide and replace the Zulip badge with a Discourse badge in README.rst. Quoting the dev guide, section 2.4. Zulip: "This is no longer actively monitored by core devs. Consider asking your questions on Discourse or on the python-dev mailing list." See also: - https://python.zulipchat.com - https://devguide.python.org/help/#zulip - https://discuss.python.org/t/discourse-github-integration/355 - https://github.com/python/devguide/issues/625 - https://github.com/python/devguide/pull/630 ---------- assignee: docs@python components: Documentation messages: 390016 nosy: Mariatta, docs@python, erlendaasland, willingc priority: normal severity: normal status: open title: Replace Zulip badge with Discourse badge in README _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43700> _______________________________________

3 7

[issue43549] Outdated descriptions for configuring valgrind.
by Xinmeng Xia 02 Apr '21

02 Apr '21

New submission from Xinmeng Xia <xiaxm(a)smail.nju.edu.cn>: At line 12-20, cpython/Misc/README.valgrind, the descriptions are out of date. File "Objects/obmalloc.c" does not contain Py_USING_MEMORY_DEBUGGER any more since Python 3.6. The descriptions should be modified for Python 3.6-3.10 Attached line 12-20, cpython/Misc/README.valgrind: ================================================= If you don't want to read about the details of using Valgrind, there are still two things you must do to suppress the warnings. First, you must use a suppressions file. One is supplied in Misc/valgrind-python.supp. Second, you must do one of the following: * Uncomment Py_USING_MEMORY_DEBUGGER in Objects/obmalloc.c, then rebuild Python * Uncomment the lines in Misc/valgrind-python.supp that suppress the warnings for PyObject_Free and PyObject_Realloc ================================================= ---------- assignee: docs@python components: Documentation messages: 389052 nosy: docs@python, xxm priority: normal severity: normal status: open title: Outdated descriptions for configuring valgrind. type: behavior versions: Python 3.10, Python 3.6, Python 3.7, Python 3.8, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43549> _______________________________________

1 1

[issue43677] Documentation
by Daniel Torres 02 Apr '21

02 Apr '21

New submission from Daniel Torres <dto(a)fastmail.com>: https://github.com/python/cpython/blob/master/Doc/howto/descriptor.rst Section 'Functions and methods' The provided example contains comment 'Emulate Py_MethodType in Objects/classobject.c' But Py_MethodType is nowhere to be found under 'Objects/classobject.c' ---------- assignee: docs@python components: Documentation messages: 389878 nosy: danielcft, docs@python priority: normal severity: normal status: open title: Documentation type: enhancement versions: Python 3.10 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43677> _______________________________________

5 9

[issue43697] Importlib documentation does not cover how meta path finders should handle namespace packages
by Brett Cannon 02 Apr '21

02 Apr '21

Brett Cannon <brett(a)python.org> added the comment: > What I've never really got clear in my mind is how dotted names get handled. Essentially: 1. Check if parent is imported; if not then import (working your way all the way back to the top if necessary) 2. Ask the sys.meta_path finders if they can handle the module 3. Use the loader from the spec 4. Add the imported module as an attribute on the parent If you start from https://github.com/python/cpython/blob/master/Lib/importlib/__init__.py#L108 you can see how it all works. The Python code is actually not that complicated, especially if you ignore all the old PEP 302 compatibility code 😉. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43697> _______________________________________

1 0

[issue43697] Importlib documentation does not cover how meta path finders should handle namespace packages
by Paul Moore 02 Apr '21

02 Apr '21

Paul Moore <p.f.moore(a)gmail.com> added the comment: > if they return a spec they can, if they don't then they can't What I've never really got clear in my mind is how dotted names get handled. But that's probably just a matter of needing to experiment a bit (I don't think it's particularly complicated, I just need to get a better feel for it). > https://docs.python.org/3/reference/import.html#namespace-packages Ouch. I'd completely missed how much there is in there. Sorry about that, I should have done my research. Thanks for the help. ---------- _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43697> _______________________________________

1 0

[issue43697] Importlib documentation does not cover how meta path finders should handle namespace packages
by Brett Cannon 02 Apr '21

02 Apr '21

Change by Brett Cannon <brett(a)python.org>: ---------- assignee: brett.cannon -> docs@python nosy: +docs@python _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43697> _______________________________________

1 0

[issue43698] Use syntactically correct examples on abc package page
by Vladimir Ryabtsev 02 Apr '21

02 Apr '21

New submission from Vladimir Ryabtsev <greatvovan(a)gmail.com>: There are code snippets on the package's page (https://docs.python.org/3.10/library/abc.html) like this: class C(ABC): @classmethod @abstractmethod def my_abstract_classmethod(cls, ...): ... Here, the author probably wanted to demonstrate that the method may have _any other arguments_ in addition to `cls`, but it makes the code not compilable: def my_abstract_classmethod(cls, ...): ^ SyntaxError: invalid syntax Additionally it uses the same Ellipsis as in the method's body (that is supposed to indicate a stub), which is confusing. I think that all code samples must be syntactically correct, so that if a reader copypastes them into their code editor they would work right away. I suggest to remove ellipsis in the argument lists everywhere on the page and replace them with one of the following: - sample parameters such as `a, b, c` or `my_arg1, my_arg2`, - `*args, **kwargs`, - nothing. ---------- assignee: docs@python components: Documentation messages: 390004 nosy: Vladimir Ryabtsev, docs@python priority: normal severity: normal status: open title: Use syntactically correct examples on abc package page type: compile error versions: Python 3.10, Python 3.8, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43698> _______________________________________

1 0

[issue43670] Typo in 3.10 changelog
by Ilya Gruzinov 01 Apr '21

01 Apr '21

New submission from Ilya Gruzinov <shagren(a)gmail.com>: In next lines typo in function `load`: # BUG: "rb" mode or encoding="utf-8" should be used. with open("data.json") as f: data = json.laod(f) ---------- assignee: docs@python components: Documentation messages: 389825 nosy: docs@python, shagren priority: normal pull_requests: 23843 severity: normal status: open title: Typo in 3.10 changelog versions: Python 3.10 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43670> _______________________________________

2 1