Brooke Storm added the comment:
To answer Steve's question, the ver command gives me:
Microsoft Windows [Version 10.0.18917.1000]
Thank you for looking into this.
--
___
Python tracker
<https://bugs.python.org/is
Brooke Storm added the comment:
I should add that, after testing a bit, it isn't actually working in cmd.exe.
That is simply using the overarching python install. It's not using the
virtualenv at all. The virtualenv that was created by the venv module appears
to be non-fun
New submission from Brooke Storm :
I am finding that, using Powershell on Windows 10 and the current version of
Python 3.7.3 installed from the Microsoft Store, when I create a virtualenv via
"python -m venv " and activate it in Powershell with the Activate.ps1
script that is gene
