docs May 2021

docs@python.org

9 participants
53 discussions

[issue43997] dataclasses documentation needs version added for match_args, kw_only, and slots
by Shreyan Avigyan 02 May '21

02 May '21

Change by Shreyan Avigyan <shreyan.avigyan(a)gmail.com>: ---------- nosy: +shreyanavigyan _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43997> _______________________________________

1 0

[issue41277] documentation: os.setxattr() errno EEXIST and ENODATA
by Eric V. Smith 01 May '21

01 May '21

Change by Eric V. Smith <eric(a)trueblade.com>: ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue41277> _______________________________________

1 0

[issue41277] documentation: os.setxattr() errno EEXIST and ENODATA
by miss-islington 01 May '21

01 May '21

Change by miss-islington <mariatta.wijaya+miss-islington(a)gmail.com>: ---------- pull_requests: +24485 pull_request: https://github.com/python/cpython/pull/25795 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue41277> _______________________________________

1 0

[issue41277] documentation: os.setxattr() errno EEXIST and ENODATA
by miss-islington 01 May '21

01 May '21

Change by miss-islington <mariatta.wijaya+miss-islington(a)gmail.com>: ---------- nosy: +miss-islington nosy_count: 5.0 -> 6.0 pull_requests: +24484 pull_request: https://github.com/python/cpython/pull/25794 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue41277> _______________________________________

1 0

[issue41277] documentation: os.setxattr() errno EEXIST and ENODATA
by Eric V. Smith 01 May '21

01 May '21

Eric V. Smith <eric(a)trueblade.com> added the comment: Sorry, ZackerySpytz. I saw PR 25742 first and reviewed and merged it before I saw that you have an earlier PR on this issue. ---------- nosy: +eric.smith _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue41277> _______________________________________

1 0

[issue43815] documentation for types.new_class() mention misleading default for exec_body
by Eric V. Smith 01 May '21

01 May '21

New submission from Eric V. Smith <eric(a)trueblade.com>: https://github.com/python/cpython/blob/3.8/Lib/types.py The documentation says "If no callback is provided, it has the same effect as passing in lambda ns: ns." I read this as saying that the callback should return the namespace, but in reality the return value is ignored. I think the lambda should be "lambda ns: None". ---------- assignee: docs@python components: Documentation keywords: easy, newcomer friendly messages: 390854 nosy: docs@python, eric.smith priority: normal severity: normal status: open title: documentation for types.new_class() mention misleading default for exec_body versions: Python 3.10, Python 3.8, Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43815> _______________________________________

3 4

Example of uniform on random page appears to have the wrong comment
by Theodore Greene 01 May '21

01 May '21

Hi! I'm a little confused. In the examples section of the docs for the random module it shows uniform(2.5, 10.0) # Random float: 2.5 <= x < 10.0 But the docs say random.uniform(a, b) Return a random floating point number N such that a <= N <= b for a <= b and b <= N <= a for b < a. So, shouldn't the example really say # Random float: 2.5 <= x <= 10.0 or am I not understanding random.uniform? Best wishes, Ted

2 1

[issue43971] documentation: no spacing around default args in annotated function
by Mohamed Moselhy 01 May '21

01 May '21

New submission from Mohamed Moselhy <look4d(a)gmail.com>: See https://www.python.org/dev/peps/pep-0008/#function-annotations The first section of https://docs.python.org/3/library/dataclasses.html shows quantity_on_hand: int=0, when there should be spacing around the '=' according to PEP 8 (see link above). ---------- assignee: docs@python components: Documentation files: screen.png messages: 392271 nosy: docs@python, eric.araujo, ezio.melotti, mdk, moselhy, willingc priority: normal severity: normal status: open title: documentation: no spacing around default args in annotated function versions: Python 3.10, Python 3.11, Python 3.7, Python 3.8, Python 3.9 Added file: https://bugs.python.org/file49998/screen.png _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43971> _______________________________________

4 8

[issue43869] Fix documentation of epoch/time.time
by Ofek Lev 01 May '21

01 May '21

New submission from Ofek Lev <ofekmeister(a)gmail.com>: The descriptions for the following: - https://docs.python.org/3/library/time.html#epoch - https://docs.python.org/3/library/time.html#time.time indicate that it is platform dependent. However, that is likely untrue. See the brief discussion here: https://github.com/DataDog/integrations-core/pull/6692#discussion_r427469097 ---------- assignee: docs@python components: Documentation messages: 391214 nosy: Ofekmeister, docs@python, p-ganssle priority: normal severity: normal status: open title: Fix documentation of epoch/time.time type: enhancement 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/issue43869> _______________________________________

3 5

[issue36384] [security] CVE-2021-29921: ipaddress Should not reject IPv4 addresses with leading zeroes as ambiguously octal
by Michał Górny 01 May '21

01 May '21

Michał Górny <mgorny(a)gentoo.org> added the comment: > If it takes years for users to get to 3.10, we should reevaluate our > release cycle, not whether we aggressively break maintenance releases. I don't really understand how that would help. The problem is that users have major inertia for switching to newer Python versions. A part of it is that a lot of people just don't care about deprecation warnings, and don't fix stuff until it's actually broken. In the end, your projects are blocked from using new major Python version by broken dependencies with long release cycles. I can't imagine deliberately leaving 3.8 and 3.9 vulnerable when 3.10 isn't going to reach final release in the next half year. Gentoo stable is only switching to 3.9 next month. I'm pretty sure some of our (few) corporate users are still on 3.7 or earlier. Then, there are projects that literally include a vulnerable copy of Python 2.7 to get around distributions removing it. I dare say this has less breakage potential than the &/; change. It should be fixed on all affected versions. If you don't do that, distributions will have to patch it anyway, and this will only lead to incompatibility between different Python package vendors. ---------- nosy: +mgorny _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue36384> _______________________________________

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

docs May 2021