New submission from Chris Tse :
Following up on https://bugs.python.org/issue37369 as it was advised to open a
new issue regarding case sensitivity.
I am on Windows 10 running Version 10.0.19041 Build 19041. I am experiencing
the same problem in that issue when using venv on Powershell.
The
Change by Chris Tse :
--
type: -> behavior
___
Python tracker
<https://bugs.python.org/issue41925>
___
___
Python-bugs-list mailing list
Unsubscrib
Chris Tse added the comment:
UPDATE:
After some further investigation, it seems like even on cmd and seeing the
(myenv) indicator, it actually seems to be falling back to system pip and
installing packages globally. Running `.\myenv\Scripts\pip.exe` actually throws
that same error. CMD
Chris Tse added the comment:
Another update:
After a full shutdown from yesterday and trying again today, everything seems
to be working now, including activating the venv via:
1. python -m venv myenv
2. .\myenv\Scripts\activate (not Activate.ps1, though that work too, is this
intended
