[issue46950] Windows 11, VENV not working with case sensitive windows paths

Eryk Sun added the comment: In 3.10, you should be able to work around the problem for the venv site-packages directory by setting the environment variable "PYTHONPLATLIBDIR" to "Lib". This sets sys.platlibdir, which the site module uses to create the site-packages directory. The default

[issue46950] Windows 11, VENV not working with case sensitive windows paths

Steve Dower added the comment: Okay, so that means there's some code somewhere that has a lowercase "lib". If you change it back to "Lib", can you do "python -m pip"? If that works, but a direct "pip" does not, it'll be an issue in pip (or a dependency), as those executables are generated

[issue46950] Windows 11, VENV not working with case sensitive windows paths

Darrel O'Pry added the comment: renaming Lib to lib seems to also resolve the problem... -- ___ Python tracker ___ ___

[issue46950] Windows 11, VENV not working with case sensitive windows paths

Steve Dower added the comment: As a quick (wild) guess, is it expecting the "Lib" directory to be lowercase "lib"? Could you try renaming that directory in your venv and see if it changes anything? -- ___ Python tracker

[issue46950] Windows 11, VENV not working with case sensitive windows paths

Darrel O'Pry added the comment: I've done some additional troubleshooting today. I have case sensitivity enabled in my git checkouts where I am creating the virtual env. I do this for a more consistent cross-platform experience for managing code with team members also using linux and macos.