One of the most important things is that I was **not informed** about how this affects the release
process and we ended up with a venv packaged in the tarball, unfortunately.

I agree that these changes should be notified to the release manager, precisely to avoid these situations.

I am trying to republish the tarball without the venv.


On Wed, 4 Aug 2021 at 10:53, Miro Hrončok <> wrote:
On 04. 08. 21 11:28, Petr Viktorin wrote:
> Hi,
> A recent change "make html" in the Doc directory create a venv if one wasn't
> there before. If you don't want to download sphinx and other dependencies from
> PyPI, you'll need to adjust your workflow.
> If you already have all the dependencies, the following command (in the CPython
> directory, not Doc) will build docs for you:
>       sphinx-build Doc Doc/build/
> The issue that added this is:

For what it's worth, I think that:

  - changes in the workflow should be discussed first
  - changes like this should not happen this late in the release cycle
  - a documented/supported way to build the docs with make without venv should
    exist (currently, running `mkdir venv` before `make ...` kinda works)

Miro Hrončok
Phone: +420777974800
IRC: mhroncok

Python-Dev mailing list --
To unsubscribe send an email to
Message archived at
Code of Conduct: