Paul Moore added the comment:
Sigh. Never mind, this appears to be because virtualenv uses its own hacked
copy of site.py which is missing a lot of the venv support code.
I'll report this over on virtualenv.
--
resolution: -> third party
stage: -> resolved
status: open -> closed
_
Paul Moore added the comment:
Further update - this appears to also happen on Ubuntu (at least the version
available through the Windows Linux subsystem), so it's not a Windows-specific
issue.
--
assignee: steve.dower ->
___
Python tracker
Paul Moore added the comment:
This appears to be somehow caused by running Python 3.7.4 from an active
virtualenv (which I'd forgotten I had active when I did the test).
Regardless, I'd have expected that the command would either correctly create a
venv containing pip, or fail to create the
New submission from Paul Moore :
The venv module with Python 3.4 on Windows doesn't install pip - even though
the --without-pip flag is not specified. This appears to be a regression since
pip is installed when using 3.7:
>C:\Utils\PythonVersions\Python-3.7.3\python.exe -m venv ve-373
>dir .\