[issue37369] Issue with pip in venv on Powershell in Windows

Eryk Sun added the comment: Case-sensitive file access is potentially possible with FILE_FLAG_POSIX_SEMANTICS (CreateFileW) and FIND_FIRST_EX_CASE_SENSITIVE (FindFirstFileExW). These flags make the API omit the object-manager flag OBJ_CASE_INSENSITIVE in the NtCreateFile or NtOpenFile

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: > The problem is that Powershell has case-sensitive commands and pip is trying > to call path completely in minor case This is not normal configuration. I'm not sure what you've done here, but please open a new issue with details about how you enabled

[issue37369] Issue with pip in venv on Powershell in Windows

Federico Tabbò added the comment: Hello and sorry for reopening this issue but I have it as well. The problem is that Powershell has case-sensitive commands and pip is trying to call path completely in minor case PS C:\Users\federico.Tabbo\git\nexus2aci\env\Scripts> .\Activate.ps1 (env) PS

[issue37369] Issue with pip in venv on Powershell in Windows

Miika Mäkelä added the comment: I tried to reproduce the issue on a another windows installation (Windows build 10.0.18363.0), but was however unable to do it following the same steps. I fear that my original python/pip installation is just corrupted somehow due to having many python

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: Hi Miika Please create a new issue. It would also be helpful if you gave us some idea of what your username looks like, even if you change it a bit to hide it from the internet. The most common cause of this error is spaces or non-ASCII characters in your

[issue37369] Issue with pip in venv on Powershell in Windows

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37369] Issue with pip in venv on Powershell in Windows

miikama added the comment: Hi, First time reporting so feel free to direct me to a better place if this is not the correct place :) I am still facing the issue that started this thread with Python 3.8 and 3.9. Steps to reproduces 1. Clean install of Python 3.9.0b3 (quick install via .exe

[issue37369] Issue with pip in venv on Powershell in Windows

gaborbernat added the comment: A note on the above points, virtualenv has started migrating over to venv via https://github.com/pypa/virtualenv/pull/1377 . Following this, the old ways of virtualenv should be left to the history books. Hopefully, I can get it out within the next month or

[issue37369] Issue with pip in venv on Powershell in Windows

Paul Moore added the comment: On Fri, 5 Jul 2019 at 21:33, Steve Dower wrote: > Yeah. We probably need to be clear about which approaches are actually > supported and which ones are not. > > Ultimately though, I think this is a situation where the breakage is forced > upon us (by the

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: > I'm pretty sure there is code in the wild that expects / > python.exe to be the Python executable (when you're not in a virtual > environment) ... for example, when getting > sys.prefix from the registry (um, I don't think that's right, as the > executable

[issue37369] Issue with pip in venv on Powershell in Windows

Paul Moore added the comment: On Thu, 27 Jun 2019 at 18:08, Steve Dower wrote: > However, it does mean that we need to start reporting a sys.executable that > is not inside sys.prefix, and I'm not sure whether that is a good idea. > > Looking at venv (+Vinay for confirmation here), it seems

[issue37369] Issue with pip in venv on Powershell in Windows

Ned Deily added the comment: New changeset 3c34ea97a341e4dd80b542c99c593f014a8ae410 by Ned Deily (Steve Dower) in branch '3.7': bpo-37369: Fixes path for sys.executable when running from the Microsoft Store (GH-14450)

[issue37369] Issue with pip in venv on Powershell in Windows

Change by Steve Dower : -- assignee: -> steve.dower ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: > I'm not sure of the purpose of sys._base_executable. Maybe open a separated > issue to make the attribute public? I'm not sure if multiprocessing (for > example) should use it, or if sys.executble should be used. Yeah, it's a bit more complex. Sometimes it's

[issue37369] Issue with pip in venv on Powershell in Windows

Change by Steve Dower : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: New changeset 323e743d4879f1cd861d0b252775797fb7938755 by Steve Dower in branch '3.8': bpo-37369: Fix initialization of sys members when launched via an app container (GH-14467) https://github.com/python/cpython/commit/323e743d4879f1cd861d0b252775797fb7938755

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: New changeset ac14632c756fec561e4b868b8793334bd7b22241 by Steve Dower in branch 'master': bpo-37369: Fixes crash when reporting fatal error (GH-14468) https://github.com/python/cpython/commit/ac14632c756fec561e4b868b8793334bd7b22241 --

[issue37369] Issue with pip in venv on Powershell in Windows

Change by Steve Dower : -- pull_requests: +14285 pull_request: https://github.com/python/cpython/pull/14468 ___ Python tracker ___

[issue37369] Issue with pip in venv on Powershell in Windows

Change by Steve Dower : -- pull_requests: +14284 pull_request: https://github.com/python/cpython/pull/14467 ___ Python tracker ___

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: New changeset 9048c49322a5229ff99610aba35913ffa295ebb7 by Steve Dower in branch 'master': bpo-37369: Fix initialization of sys members when launched via an app container (GH-14428)

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: New changeset db4eb2c57dbfca402a539184c966c449cb1aa8e3 by Steve Dower in branch '3.7': bpo-37369: Fix path handling when python.exe is used as a symlink (GH-14461) https://github.com/python/cpython/commit/db4eb2c57dbfca402a539184c966c449cb1aa8e3 --

[issue37369] Issue with pip in venv on Powershell in Windows

Change by Steve Dower : -- pull_requests: +14278 pull_request: https://github.com/python/cpython/pull/14461 ___ Python tracker ___

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: New changeset ed4657bd28432ace671a9e6ae38a3d485c69213d by Steve Dower in branch '3.7': bpo-37369: Fix venv and test symlinking (GH-14456) https://github.com/python/cpython/commit/ed4657bd28432ace671a9e6ae38a3d485c69213d --

[issue37369] Issue with pip in venv on Powershell in Windows

Change by Steve Dower : -- pull_requests: +14273 pull_request: https://github.com/python/cpython/pull/14456 ___ Python tracker ___

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: New changeset db4d7ddb012ef8f087a8eb2a5b8a672d04a48e1a by Steve Dower in branch '3.7': bpo-37369: Fixes path for sys.executable when running from the Microsoft Store (GH-14450) https://github.com/python/cpython/commit/db4d7ddb012ef8f087a8eb2a5b8a672d04a48e1a

[issue37369] Issue with pip in venv on Powershell in Windows

Change by Steve Dower : -- pull_requests: +14266 pull_request: https://github.com/python/cpython/pull/14450 ___ Python tracker ___

[issue37369] Issue with pip in venv on Powershell in Windows

STINNER Victor added the comment: > For 3.8 I can apply the same fix and make sys.base_executable public, or keep > it as sys._base_executable. Either way, it'll show up in PyConfig. (Victor - > thoughts here? Should be a non-breaking change, right?) There is _PyConfig._config_version which

[issue37369] Issue with pip in venv on Powershell in Windows

Eryk Sun added the comment: > you should go through your current user's apps directory > (C:\Users\name\AppData\Local\Microsoft\WindowsApps\, > which contains only symlinks to the actual executables). "%LocalAppData%\Microsoft\WindowsApps" contains IO_REPARSE_TAG_APPEXECLINK reparse points.

[issue37369] Issue with pip in venv on Powershell in Windows

Change by Steve Dower : -- keywords: +patch pull_requests: +14244 stage: -> patch review pull_request: https://github.com/python/cpython/pull/14428 ___ Python tracker ___

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: So I have a fix for 3.9 for this, I believe (involves making sys.base_executable configurable via PyConfig and overriding it and config->home when we know we're inside an app container). For 3.8 I can apply the same fix and make sys.base_executable public, or

[issue37369] Issue with pip in venv on Powershell in Windows

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

[issue37369] Issue with pip in venv on Powershell in Windows

Ned Deily added the comment: OK, I"m bumping it to "deferred blocker" for now so it remains visible. -- priority: critical -> deferred blocker ___ Python tracker ___

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: This seems to be a change in Windows at some point, as it still works on one of my other PCs. I've pinged some colleagues to find out what might have happened, but it definitely looks like the lack of Read+Execute permission is working correctly now :( One

[issue37369] Issue with pip in venv on Powershell in Windows

Steve Dower added the comment: Okay, this definitely used to work, but now it's broken for me too. What version of Windows are you on (copy-paste from cmd.exe's ver command)? -- ___ Python tracker

[issue37369] Issue with pip in venv on Powershell in Windows

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-functional at

[issue37369] Issue with pip in venv on Powershell in Windows

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 generated, pip