Mailman 3 January 2021 - docs

[issue20464] Update distutils sample config file in Doc/install/index.rst
by Zachary Ware 03 Feb '21

03 Feb '21

New submission from Zachary Ware: >From docs@: On Thu, Jan 16, 2014 at 2:56 AM, Peter Bröcker <peter.broecker(a)uni-koeln.de> wrote: > Hi, > > I have tried to set up the distutils config files for a custom module > installation. Using the suggested snippet from > > http://docs.python.org/2/install/ > > [install] > install-base=$HOME/python > install-purelib=lib > install-platlib=lib.$PLAT > install-scripts=scripts > install-data=data did not work for me. > > Instead, I had to add install-headers and additionally modify all paths > to include $base: > > [install] > install-base=/some/dir > install-purelib=$base/lib > install-platlib=$base/lib.$PLAT > install-scripts=$base/scripts > install-headers=$base/include > install-data=$base/data > > > I'm unsure if this is actually a bug, but I could only resolve this with > the help of this answer on stackoverflow: > http://stackoverflow.com/a/12768721 > > Best regards, > Peter ---------- assignee: docs@python components: Distutils, Documentation messages: 209829 nosy: docs@python, zach.ware priority: normal severity: normal stage: test needed status: open title: Update distutils sample config file in Doc/install/index.rst type: behavior versions: Python 2.7, Python 3.3, Python 3.4 _______________________________________ Python tracker <report(a)bugs.python.org> <http://bugs.python.org/issue20464> _______________________________________

3 4

[issue43082] descriptor howto: typo in "Definition and introduction"
by diegoe 02 Feb '21

02 Feb '21

New submission from diegoe <diegoe(a)gnome.org>: In https://docs.python.org/3.10/howto/descriptor.html#definition-and-introduct… The paragraph reads: """ Definition and introduction In general, a descriptor is an attribute value that has one of the methods in the descriptor protocol. Those methods are __get__(), __set__(), and __delete__(). If any of those methods are defined for an the attribute, it is said to be a descriptor. """ I believe it should be either "an attribute" or "the attribute" in the last sentence. Probably missed it because both options would read fine. ---------- assignee: docs@python components: Documentation messages: 386011 nosy: diegoe, docs@python priority: normal severity: normal status: open title: descriptor howto: typo in "Definition and introduction" type: enhancement versions: Python 3.10 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43082> _______________________________________

3 6

[issue43056] Use of dicts in sections 4.2 and 4.7 of Python tutorial a bit confusing
by Jesse Silverman 01 Feb '21

01 Feb '21

New submission from Jesse Silverman <jessevsilverman(a)gmail.com>: The Python tutorial was not my first introduction to Python, but I see things in sections 4.2 and 4.7 that likely would have confused me a lot if it was. In 4.2 near the end, we have great advice about how to avoid problems with modifying a collection while iterating thru it. Unfortunately, it both makes use of a dict despite not having introduced it before at all within the tutorial (I wasn't shocked because it was NOT my first introduction to Python) and in fact, the .items() method which is beautifully explained in section 5.6, which hasn't been read yet. I got thru it a bit shakily, and in a reference, rather than an introductory tutorial, it is quite literally impossible to present everything in a strict sequence, but I would definitely have been thrown for a loop if it was actually my first introduction to Python. All was good again until I got to section 4.7.2, where I was again glad I had previously consumed tutorial materials concerning dict. There is a forward reference to: https://docs.python.org/3.9/library/stdtypes.html#typesmapping Which every Python programmer should undoubtedly be familiar with eventually, but "why not?" to the more novice-friendly: https://docs.python.org/3.9/tutorial/datastructures.html#dictionaries The forward reference from this section to tuples in section 5 of the tutorial suggests that this might have been appropriate as well. The dict, the tuple and parameter passing are all very basic topics indeed, but I would have found 4.7 very rough going if I had no prior exposure to dict and tuple. This isn't a complaint demanding a refund for the cost of the tutorial, so much as an indication of where I think true novices attempting to follow the tutorial in sequence would likely be thrown for a loop. I understand there is a healthy ecosystem of free and paid introductory tutorial material for Python, as evidenced by the fact that I was only working thru the tutorial just now, having been referred to it as a pre-req for other material I will be moving on to soon. ---------- assignee: docs@python components: Documentation messages: 385870 nosy: docs@python, jessevsilverman priority: normal severity: normal status: open title: Use of dicts in sections 4.2 and 4.7 of Python tutorial a bit confusing versions: Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43056> _______________________________________

3 3

[issue43087] ctypes documentation error
by Zackery Spytz 31 Jan '21

31 Jan '21

Zackery Spytz <zspytz(a)gmail.com> added the comment: Thank you for the report. ---------- versions: +Python 3.10, Python 3.8 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43087> _______________________________________

1 0

[issue43087] ctypes documentation error
by Zackery Spytz 31 Jan '21

31 Jan '21

Change by Zackery Spytz <zspytz(a)gmail.com>: ---------- keywords: +patch nosy: +ZackerySpytz nosy_count: 2.0 -> 3.0 pull_requests: +23219 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24404 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43087> _______________________________________

1 0

[issue43087] ctypes documentation error
by Mark Tolonen 31 Jan '21

31 Jan '21

Change by Mark Tolonen <metolone(a)hotmail.com>: ---------- assignee: -> docs@python components: +Documentation, ctypes nosy: +docs@python versions: +Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43087> _______________________________________

1 0

[issue43059] sqlite3: Externally developed?
by user1347091 31 Jan '21

31 Jan '21

New submission from user1347091 <accounts(a)lrose.de>: In the documentation of the sqlite3 module it says: See also: https://github.com/ghaering/pysqlite The pysqlite web page – sqlite3 is developed externally under the name “pysqlite”. However, the README.md of the linked repository says: This project is not actively maintained any more: You are better off using the "sqlite3" module in the Python standard library, which originated from the pysqlite codebase. Which information is correct? They seem contraticting to me. It looks like this is old information from times where sqlite3 wasn't integrated in the Python standard library yet - or am I missing something? ---------- assignee: docs@python components: Documentation messages: 385884 nosy: docs@python, user1347091 priority: normal severity: normal status: open title: sqlite3: Externally developed? type: enhancement versions: Python 3.10 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43059> _______________________________________

8 14

[issue43079] wrong IP address range given for ipv4_mapped
by Al 30 Jan '21

30 Jan '21

New submission from Al <awpythonbugs(a)sunnyside.com>: https://docs.python.org/3.9/library/ipaddress.html This documentation for the 'ipaddress' IPv4/IPv6 Manipulation Library incorrectly states the address range for 'ipv4_mapped' as ::FFFF/96 (which means 0:0:0:0:0:0:0:FFFF/96). This is just flat out wrong. There are some websites out there, e.g. APNIC, that also have this error. The correct address range can be expressed by any of the following methods: 1) 0:0:0:0:0:FFFF:0:0/96 2) ::FFFF:0:0/96 3) 0:0:0:0:0:FFFF::/96 ---------- assignee: docs@python components: Documentation messages: 385999 nosy: alwhaley, docs@python priority: normal severity: normal status: open title: wrong IP address range given for ipv4_mapped 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/issue43079> _______________________________________

1 0

[issue43034] Python tutorial misleads users about floor division behavior
by Jesse Silverman 29 Jan '21

29 Jan '21

New submission from Jesse Silverman <jessevsilverman(a)gmail.com>: I had never worked thru the Python tutorial, it's kind of awesome. I noticed multiple independent presenters incorrectly describe the behavior of floor division when the signs of the operands don't match. Not just sloppy ones, some who are usually pretty careful -- people forget. I found it odd. Today I read: https://docs.python.org/3.9/tutorial/introduction.html#using-python-as-a-ca… 'Division (/) always returns a float. To do floor division and get an integer result (discarding any fractional result) you can use the // operator; to calculate the remainder you can use %:' I know what they mean (there will never be a non-zero fractional component in the result) however, stating that it "discards any fraction result" explicitly suggests that it will round towards zero for all results. The name of the operator tells us the true story, as does a test, it rounds towards negative infinity for all results. Hopefully all the people using Python to treat cancer, fly to Mars and run power plants know what the behavior is. However, anecdotally, I have seen evidence that generally cautious, fairly-detail oriented programmers seem to forget the details of the behavior, this is one place in the docs from which many people first learn about the floor division operator and this page would lead me to believe it operates differently than it does in reality. If the words right there don't get changed, or the example of -10/3 doesn't get added, would this be a good excuse for a third footnote? I would actually wish for both the wording to be changed and to show an example like -10 / 3, tho admittedly I came from an Engineering background so I am always worried someone's going to blow up somewhere... Deepest regards for everyone who gets to regularly close the complaints about floor division working as designed and documented -- but not quite documented on this page which more people may read than others covering the operator. ---------- assignee: docs@python components: Documentation messages: 385746 nosy: docs@python, jessevsilverman priority: normal severity: normal status: open title: Python tutorial misleads users about floor division behavior versions: Python 3.9 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue43034> _______________________________________

3 3

[issue14191] argparse doesn't allow optionals within positionals
by Tadek Kijkowski 29 Jan '21

29 Jan '21

Change by Tadek Kijkowski <tkijkowski(a)gmail.com>: ---------- pull_requests: +23191 pull_request: https://github.com/python/cpython/pull/24367 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue14191> _______________________________________

1 0