Mailman 3 May 2021 - docs

error in docs
by guyrenebongers71 04 Jun '21

04 Jun '21

Hello I start off this email with wishing everybody a good health. The documentation python tutorial release 3.6.10 has got an error. paragraph 2.1.1 Argument parsing it reads : when no script and no arguments are given, sys.argv[0] is an empty string. When the script name is given as '-' (meaning standard input), sys.argv[0] is set to '-'. When -c command is used, sys.argv[0] is set to '-c'. When -m module is used, sys.argv[0] is set to the full name of the located module. Options found after -c command or -m module are not consumed by the Python interpreter’s option processing but left in sys.argv for the command or module to handle. That should be sys.argv[1]. sys.argv[0] gives the full path of the interpreted used. An example: In [2]: print(sys.argv) ['/usr/bin/ipython3', '-c', 'print("data")', '-i'] I used python 3.8.5 ------------------------------------------------------ Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

os.setxattr
by Languedoc, Kevin 27 May '21

27 May '21

Hi, In the 3.9.5 documentation in the os module, the setxattr is listed https://docs.python.org/3/library/os.html#os.setxattr but the os.py source file doesn't have that function https://github.com/python/cpython/blob/3.9/Lib/os.py Has this functionality been removed or moved to another module? Thanks Kevin Languedoc Data Engineering Specialist SPÉCIALISTE EN INGÉNIERIE DE DONNÉES VICE-PRÉSIDENCE TECHNOLOGIES DE L'INFORMATION TÉL. : 438.680.3286 / FACEBOOK.COM/CCQ [cid:image001.png@01D74C8D.3EF5B9F0] DEVEZ-VOUS VRAIMENT IMPRIMER CE COURRIEL? PENSONS ENVIRONNEMENT. AVIS DE CONFIDENTIALITÉ L'information contenue dans ce message est de nature privilégiée et confidentielle. Elle ne peut être utilisée que par la personne ou l'entité dont le nom apparaît ci-dessus. Si le lecteur de ce message n'est pas le destinataire prévu, il est prié de noter qu'il est strictement interdit de divulguer, de distribuer ou de copier ce message. Si ce message vous a été transmis par erreur, veuillez nous en aviser immédiatement et supprimer cette copie.

2 2

Python notes
by Natasha Ricky 20 May '21

20 May '21

Hello there i really need help to study python, will you help me send some notes or documents regarding python? thank you

2 2

Fwd: Can you explain to me this confusion?
by Tung Anh Nguyen 18 May '21

18 May '21

---------- Forwarded message --------- Từ: Tung Anh Nguyen <nvta1761999(a)gmail.com> Date: Th 2, 17 thg 5, 2021 vào lúc 16:34 Subject: Can you explain to me this confusion? To: <python-list(a)python.org> I'm using Python 3.8.5 on Ubuntu 20.04. I just don't understand these things? >>> float("8.1")*100 810.0 >>> float("8.2")*100 819.9999999999999 ? >>> float("8.3")*100 830.0000000000001 ? >>> float("8.4")*100 840.0 Why is that? Is that a bug? or something I don't know yet? Could you guys answer my question?

2 2

Opening documentation on Android.
by Aaron Twining 18 May '21

18 May '21

Hi, How can I unpack the Python documentation on Android? Thank you for your help. Aaron Twining aarontwining(a)gmail.com

3 2

A BAD BUG
by Golden Rise Studio Support 18 May '21

18 May '21

Hi, I want to report a bad bug from python IDE When I opened my source code file, it stopped and I closed it with the task manager And then I open it again and stop again and then I open it with Notepad and I see hex code "null" Please fix it and set up a backup folder for the source code And Thanks

2 1

b-p-o notifications are moving to another mailing list.
by Julien Palard 05 May '21

05 May '21

Hi docs@ readers, To enhance readability of this list and mainly to give more chance to humans posting here to receive an answer, I moved (with the help of Ee and our postmaster, thanks to them) the bugs.python.org notifications to docs-bugs@. Feel free to subscribe to docs-bugs@ if you want to receive the b.p.o notifications. => https://mail.python.org/mailman3/lists/docs-bugs.python.org/ Bests, -- [Julien Palard](https://mdk.fr)

2 1

[issue44040] Update broken link in pathlib source
by Kevin Follstad 05 May '21

05 May '21

New submission from Kevin Follstad <kfollstad(a)gmail.com>: Update broken link (repeated in several places) in pathlib sources. - # (see https://bitbucket.org/pitrou/pathlib/issue/12/) + # (see http://web.archive.org/web/20200623061726/https://bitbucket.org/pitrou/path… ) ---------- assignee: docs@python components: Documentation messages: 392960 nosy: docs@python, kfollstad priority: normal severity: normal status: open title: Update broken link in pathlib source versions: Python 3.10 _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue44040> _______________________________________

3 8

[issue44044] ConfigParser: cannot link to ConfigParser.optionxform(option)
by Jürgen Gmach 05 May '21

05 May '21

New submission from Jürgen Gmach <juergen.gmach(a)googlemail.com>: I wanted to copy a hyperlink to the documentation section for ConfigParser's optionxform method, but in https://docs.python.org/3/library/configparser.html you cannot link to this one section, as the paragraph was marked with `:noindex:` via https://github.com/python/cpython/pull/21859 / bpo-40204 The `:noindex:` workaround was introduced to silence doc build errors which came with a new Sphinx version. Without the workaround, you get errors like... P.S.: I uploaded a screenshot of the documentation section showing the heading before optionxform has a permalink, optionsxform does not. Warning, treated as error: /home/jugmac00/Projects/cpython/Doc/library/configparser.rst:1170:duplicate object description of configparser.ConfigParser.optionxform, other instance in library/configparser, use :noindex: for one of them Makefile:49: recipe for target 'build' failed make: *** [build] Error 2 Looks like a possible fix to this problem would involve a major restructuring of the configparser documentation, to avoid the "duplicated object description". Maybe there is a simpler solution? ---------- assignee: docs@python components: Documentation files: Screenshot from 2021-05-05 08-46-05.png messages: 392977 nosy: docs@python, jugmac00 priority: normal severity: normal status: open title: ConfigParser: cannot link to ConfigParser.optionxform(option) Added file: https://bugs.python.org/file50014/Screenshot from 2021-05-05 08-46-05.png _______________________________________ Python tracker <report(a)bugs.python.org> <https://bugs.python.org/issue44044> _______________________________________

2 4

[issue43354] xmlrpc.client: Fault.faultCode erroneously documented to be a string, should be int
by Jürgen Gmach 05 May '21

05 May '21

New submission from Jürgen Gmach <juergen.gmach(a)googlemail.com>: I created a XMLRPC API (via Zope), which gets consumed by a C# application. C#'s XMLRPC lib expects an `int` for the `faultCode` but I currently return a string, as this is the type which is currently documented in the official docs https://docs.python.org/3/library/xmlrpc.client.html#xmlrpc.client.Fault.fa… This leads to a `TypeMismatch` error on the client's side. The documentation for `faultCode` is pretty much unchanged since 2007, when `xmlrpc.client.rst` was first created (at least at that place) by Georg Brandl. The docs are most probably older, but I do not know where they were managed before. I had a look at the cpython source code, and at least the tests all use ints for `faultCode` (both of them :-) ) eg https://github.com/python/cpython/blob/255f53bdb54a64b93035374ca4484ba0cc1b… Having a look at the XMLRPC spec at http://xmlrpc.com/spec.md it is clearly shown that `faultCode` has to be an int. Typeshed recently added type hints for xmlrpc lib, and they used string for `faultCode` - but I guess this is just an aftereffect from the faulty documentation. https://github.com/python/typeshed/pull/3834 I suggest to both update cpython's documentation and to create a PR for typeshed in order to fix the type issue. If any core dev agrees on this, I'd like to prepare the pull requests. Thanks for taking your time to look into this! ---------- assignee: docs@python components: Documentation messages: 387866 nosy: docs@python, jugmac00 priority: normal severity: normal status: open title: xmlrpc.client: Fault.faultCode erroneously documented to be a string, should be int 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/issue43354> _______________________________________

4 6