Mailman 3 June 2021 - docs

A suggestion for improving the documentation of chapter 10.9. Data Compression
by Guy Goldner May 22, 2024

May 22, 2024

Hello dear Python gods :) I'm new at Python and was going over the documentation . This useful paragraph : https://docs.python.org/3.7/tutorial/stdlib.html#data-compression provides info for compressing text but IMHO some important additional info is needed, without which I expect nearly all users would get stuck just as I have. Moreover, while looking for a solution I noticed a lot of articles with outdated examples which no longer work - this confused me even more to the point I started suspecting something was amiss on my end... Anyhow, adding this info would do the trick : zlib works only with bytes and in Python 3.x strings are no longer bytes. Example : *>>> zlib.compress('this is a sample string which does not work in zlib because it requires bytes and not unicode')Traceback (most recent call last): File "<stdin>", line 1, in <module>TypeError: a bytes-like object is required, not 'str'>>>* Luckily Python has a very simple solution for this : encode to utf-8, compress, decode back to unicode like so : *>>> text = 'this is a sample string which does not work in zlib because it requires bytes and not unicode with chars like this »שלום '>>> encoded = text.encode()>>> text = 'this is a sample with unicode chars »שלום '>>> encoded = text.encode()>>> compressed = zlib.compress(encoded)>>> decompressed = zlib.decompress(compressed)>>> decoded = decompressed.decode()>>> len(text),len(encoded),len(compressed) #notice that compression of short strings can be larger than the original(42, 47, 54)>>> print(text,'\n',encoded,'\n',compressed)this is a sample with unicode chars »שלום b'this is a sample with unicode chars \xc2\xbb\xd7\xa9\xd7\x9c\xd7\x95\xd7\x9d ' b'x\x9c+\xc9\xc8,V\x00\xa2D\x85\xe2\xc4\xdc\x82\x9cT\x85\xf2\xcc\x92\x0c\x85\xd2\xbc\xcc\xe4\xfc\x94T\x85\xe4\x8c\xc4\xa2b\x85C\xbb\xaf\xaf\xbc>\xe7\xfa\xd4\xebs\x15\x00\xb2K\x14|'>>> text == decodedTrue* Thank you ! You are doing a great thing ! B.R., Guy Goldner

2 2

Python 3.8 Doc Download links 404
by Thomas Burette June 29, 2021

June 29, 2021

Hello, All the download links for python 3.8 (3.8.11) are returning 404. See : https://docs.python.org/3.8/download.html . It affects all formats and both packing methods. I was able to get the documentation by manually changing the download URL from 3.8.11 to 3.8.10.

2 2

Bug in math.log function
by Abhinav Gupta June 19, 2021

June 19, 2021

math.log(536870912 , 2) gives 29.000000000000004 Whereas it should give 29.0

2 1

Fwd: xml.dom.pulldom truncates string data
by simone zannini June 18, 2021

June 18, 2021

To whom it may concern, I was working with xml.dom.minidom to parse XML files but for memory usage purposes (I'm currently working with ~10GB files) I had to change module and I started using xml.dom.pulldom. Since pulldom and minidom rely on the same data structures, the processing functions used with minidom works perfectly also on the pulldom implementation, but there's something wrong with pulldom behaviour. As you can see below this is a simple for loop where I check the tagName and proceed to get the attributes I want with the get_prjna function. [image: code1.png] [image: code2.png] This function works perfectly with minidom, but with pulldom the data I get are literally truncated. The first attribute in the first row is the key of a dictionary and is in the format PRJ******, in the second row you can see that the function just can't take a full string (taking only "PRJN"). This happens also with other data. The second element of the first row is in the format "Illumina **Seq ****" and it's obvious that something is going wrong here, because it just takes some truncated strings with random lenght. The last element of the first row is "TRANSCRIPTOMIC" but again it takes incomplete strings. [image: result.png] This is for make you understand how data are stored, in this example the "PRJ******": [image: source1.png] And this is another data: [image: source2.png] Having used minidom until this morning, I can assure you that the *same* data structure that you can see in the screen is well generated using minidom, demonstrating that there's no trace of incomplete data. I think this data loss happens when using the expandNode function, but I just can't test it because the file are too large to print the content of the expandend nodes. To be as complete as possible, I tried something like: if event == pulldom.START_ELEMENT and node.tagName == "STUDY" but this error keeps happening. Thanks in advance for the help and have a nice day!

2 1

Requesting Python Documentation
by Mahesh Raju June 17, 2021

June 17, 2021

Hi Team, Kindly send me the 3.9.5 Python Documentation alongwith tutorials . Regards, MAHESH

2 1

Failed to download documentation
by 土田聖直 June 14, 2021

June 14, 2021

Hello. Thank you for the service of documentation. I couldn’t download EPUB and PDF version documentations, 404 Not Found. (Language: Japanese, Python document version: 3.9.4, Browser: Google Chrome) I could download an English version. Japanese one isn’t supported??

2 1

Re: error in docs
by Guy René Bongers June 10, 2021

June 10, 2021

I am trying to remember and reconstruct what I am talking about. I found the original message and it shows I was using ipython3 sys.argv holds a different value under ipython3 and python3. The documentation of python 3.6.10 regarding argument parsing does indeed match what you report for python3. But it behaves differently for ipython3. At least while using it interactively. But also in script processing I just tried the following script ----- begin script import sys print("argument parsing") print(sys.argv) ------- end script script processing under ipython3 does following $ ipython3 argument-parsing.py argument parsing ['/media/guy/6C62-3B50/guy/Projecten/Computer/programmeren/python/argument-parsing.py'] script processing under python3 does following $ python3 argument-parsing.py argument parsing ['argument-parsing.py'] If one is aware of the difference one can compensate for it. I currently do not have space in my life and my head to further pursuit this or programming. So I will leave at this. The documentation is correct but their is a difference in argument parsing for python 3.8 and ipython3 version 7.13.0 That can lead to errors. At least in this specific trial and for these versions specified. On 4/06/2021 16:06, Julien Palard wrote: > Hi, you're quoting a long paragraph, I don't know what's wrong in it, > let's try: > > Le 3/14/21 à 8:48 PM, guyrenebongers71 via docs a écrit : >> it reads : when no script and no arguments are given, sys.argv[0] is an >> empty string. > $ python > >>> import sys > >>> sys.argv > [''] # This one looks OK > >> When the script name is given as '-' (meaning standard input), >> sys.argv[0] is set to '-'. > $ echo "print(__import__('sys').argv)" | python - > ['-'] > # This one looks OK too. > >> When -c command is used, sys.argv[0] is set >> to '-c'. > $ python -c 'print(__import__("sys").argv)' > ['-c'] > # This one is OK too. > >> When -m module is used, sys.argv[0] is set to the full name of >> the located module. > $ echo "print(__import__('sys').argv)" > argv.py > $ python -m argv > ['/tmp/argv.py'] > > Maybe this one? "full name" could be written "full path"? > >> 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. > $ python -c "print(__import__('sys').argv)" foo bar > ['-c', 'foo', 'bar'] > # This one is true too. > > $ python -m argv foo bar > ['/home/mdk/clones/python/python-docs-fr/argv.py', 'foo', 'bar'] > # This one is true too. > > OOOhhhhhh I think I understand, you tried with ipython, not python, in > which case it's the IPython documentation that should tell it's the full > path, not the Python documentation, an I right? > > Bests, > -- > [Julien Palard](https://mdk.fr)

1 0

doc bug: multiprocessing.pool.Pool.starmap doc string points to wrong map function
by Scott Steele June 6, 2021

June 6, 2021

In the documentation for https://docs.python.org/3.11/library/multiprocessing.html#multiprocessing.p…, the mention of the `map` function links to https://docs.python.org/3.11/library/functions.html#map instead of the multiprocessing map function ( https://docs.python.org/3.11/library/multiprocessing.html#multiprocessing.p… ). Thanks! Scott ----- This is a work of ﬁction. Names, characters, places, and incidents either are the product of the writer's imagination or are used ﬁctitiously, and any resemblance to actual persons, living or dead, businesses, companies, events, or locales is entirely coïncidental.

2 1

error in docs
by guyrenebongers71 June 4, 2021

June 4, 2021

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

Tutorial 3.9.5 Issue
by mark horowitz June 4, 2021

June 4, 2021

this section, 3.1.2. Strings, contains the following phrase: This only works with two literals though perhaps it was meant to read This only works with *true* literals though [bolded only for this email] I noticed this in version 3.9.2. ...mark horowitz

3 3