All the download links for python 3.8 (3.8.11) are returning 404. See :
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.
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.
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
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
This is for make you understand how data are stored, in this example the
And this is another data:
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!
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??
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
------- end script
script processing under ipython3 does following
$ ipython3 argument-parsing.py
script processing under python3 does following
$ python3 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 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 is set to '-'.
> $ echo "print(__import__('sys').argv)" | python -
> # This one looks OK too.
>> When -c command is used, sys.argv is set
>> to '-c'.
> $ python -c 'print(__import__("sys").argv)'
> # This one is OK too.
>> When -m module is used, sys.argv is set to the full name of
>> the located module.
> $ echo "print(__import__('sys').argv)" > argv.py
> $ python -m argv
> 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?
> [Julien Palard](https://mdk.fr)
I start off this email with wishing everybody a good health.
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 is an empty string.
When the script name is given as '-' (meaning standard input), sys.argv is set to '-'. When -c command is used, sys.argv is set to '-c'. When -m module is used, sys.argv 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. sys.argv gives the full path of the interpreted used.
In : print(sys.argv)
['/usr/bin/ipython3', '-c', 'print("data")', '-i']
I used python 3.8.5
Sent with [ProtonMail](https://protonmail.com) Secure Email.
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.