This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author hroncok
Recipients docs@python, hroncok, pablogsal
Date 2021-08-04.08:52:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
When we download the signed Python-3.10.0rc1.tgz or Python-3.10.0rc1.tar.xz source tarball, we see that the Docs/venv directory contains teh actual virtual environment with #!/home/pablogsal/github/python/3.10/3.10.0rc1/Python-3.10.0rc1/Doc/venv/bin/python3 shebangs.

That means, an attempt to build the documentation (e.g. with make html) will fail with:

PATH=./venv/bin:$PATH sphinx-build -b html -d build/doctrees   -W . build/html 
/bin/sh: ./venv/bin/sphinx-build: /home/pablogsal/github/python/3.10/3.10.0rc1/Python-3.10.0rc1/Doc/venv/bin/python3: bad interpreter: No such file or directory
make: Leaving directory '/builddir/build/BUILD/Python-3.10.0rc1/Doc'
make: *** [Makefile:51: build] Error 126

I believe the venv directory should not be part of the release tarball, especially since it is unusbale from different paths than pablogsal's github/python/3.10/3.10.0rc1/Python-3.10.0rc1 directory.

Also, technically the entire effective license of the tarball is now hard to determine, since it contains many different packages.
Date User Action Args
2021-08-04 08:52:38hroncoksetrecipients: + hroncok, docs@python, pablogsal
2021-08-04 08:52:38hroncoksetmessageid: <>
2021-08-04 08:52:38hroncoklinkissue44824 messages
2021-08-04 08:52:38hroncokcreate