New submission from Miro Hrončok <m...@hroncok.cz>: 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. ---------- assignee: docs@python components: Documentation messages: 398867 nosy: docs@python, hroncok, pablogsal priority: normal severity: normal status: open title: The 3.10.0rv1 source tarballs contain the Docs/venv directory populated with pablogsal's venv versions: Python 3.11 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44824> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
