> The key purpose of this module is for when the venv module has been removed from the standard library by your Python distribution.

I find this confusing. Does Python have plan to deprecate its “venv”? It doesn’t make sense

I am pretty sure either Ubuntu and/or Debian stripped it from default Python install.

    > Differences compared to the venv module
    >
    > The code operates similarly to py -m venv --symlinks --without-pip .venv, except that:
    >
    > There are no activation scripts (you can execute python in the virtual environment directly)

Minus the non-existence of activation scripts, is this not the case with normal virtual environments? I've always been able to invoke the python executable in the virtual environment directly and be in the proper environment. I believe the activation scripts just ensure your current shell uses the virtual environment's python rather than the system one or whatever you've configured your shell to use.

I never understood the need for virtual environments like this. In windows I use batchfiles running Subst to "activate" python installations to a specific "drive" and not only does it work greatly, it's also short, simple, transparent, flawless and independent of the work of others.

When the rest of us downgrade to Windows, maybe we'll keep this post in mind.