[issue42863] Python venv inconsistent folder structure on windows
Darrel O'Pry added the comment: steve, I would be willing to champion this change. The process seems pretty straightforward. Create a release that creates the consistent layout on windows, symlinks the legacy paths, and adds some deprecation warnings. Then in a later release remove the symlinks and deprecation warnings.. Any way you would be willing to guide me through the process? -- nosy: +darrel.opry ___ Python tracker <https://bugs.python.org/issue42863> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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 <https://bugs.python.org/issue46950> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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. I have had issues in the past with case changes in filenames causing issue on projects and enabling case sensitivity has eliminate these issues when working with my counterparts on other platforms. I've tested the following with both powershell and bash. ``` mkdir test-venv-case-sensitivity cd test-venv-case-sensitivity fsutil.exe file setCaseSensitiveInfo . enable python -m venv ./venv ./venv/Scripts/Activate.ps1 pip # you should get the error "No module named 'pip' cd ./venv/ fsutil.exe file setCaseSensitiveInfo . disable pip # the command now works ``` This wasn't an issue prior to upgrading to Windows 11, so something may have changed in the handling of the case sensitivity flag on Windows. I have a venv created on windows 10, prior to my windows 11 upgrade that does work. I didn't encounter the issue until setting up an installation of Python 3.9.10 to support another project, then trying to create a new 3.10.2 venv. I can work around the issue by specifically disabling case sentitivity in my venv folders, but it would be nice if venvs worked out of the box with case sensitive filesytems on windows. It seems like some code is making assumptions about case sensitivity on windows. I found that if I disable case sensitivity in the venv folder, the venv starts working again. -- title: Windows 11 venv -> Windows 11, VENV not working with case sensitive windows paths ___ Python tracker <https://bugs.python.org/issue46950> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46950] Windows 11 venv
New submission from Darrel O'Pry : I created a virtual env on windows 11. When I run pip install -r "..." I get the error ``` C:\Users\dopry\src\Client\some.domain.com\django> pip install -r .\requirements_to_freeze.txt Traceback (most recent call last): File "C:\Users\dopry\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 196, in _run_module_as_main return _run_code(code, main_globals, None, File "C:\Users\dopry\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 86, in _run_code exec(code, run_globals) File "C:\Users\dopry\src\Client\some.domain.com\django\venv310\Scripts\pip.exe\__main__.py", line 4, in ModuleNotFoundError: No module named 'pip' ``` When I run get command to verify that the venv is activated I get ``` (venv310) PS C:\Users\dopry\src\Client\some.domain.com\django> Get-Command python CommandType Name Version Source --- --- -- Application python.exe 3.10.21... C:\Users\dopry\src\Client\some.domain.com\django\venv310\Scripts\python.exe ``` When I update the `venv310\pyenv.cfg` and set `include-system-site-packages = true` to true, it was defaulted to false, it seems that I can pip install my requirements successfully. When I try to start my app though, the requirements are not found. -- components: Windows messages: 414691 nosy: darrel.opry, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: Windows 11 venv type: crash versions: Python 3.10, Python 3.9 ___ Python tracker <https://bugs.python.org/issue46950> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
