Message360908
> Suffice to say, is there a significant reason to not allow it?
It's poorly supported by packaging. In particular, relocating an environment isn't supported with entry-point scripts, which pip installs with a fully-qualified shebang. Moreover, entry-point scripts in Windows are created as exe files (e.g. "pip.exe") that embed the fully-qualified path of python[w].exe in the environment, plus a zipped __main__.py. For example, given an environment at "C:\Temp\env", running "C:\Temp\env\Scripts\pip.exe" in turn spawns a child process with the command line: "C:\Temp\env\Scripts\python.exe" "C:\Temp\env\Scripts\pip.exe". This breaks if the environment is renamed or relocated. |
|
Date |
User |
Action |
Args |
2020-01-28 22:33:49 | eryksun | set | recipients:
+ eryksun, brett.cannon, vinay.sajip, Jeff.Edwards |
2020-01-28 22:33:48 | eryksun | set | messageid: <1580250828.98.0.597252195615.issue39469@roundup.psfhosted.org> |
2020-01-28 22:33:48 | eryksun | link | issue39469 messages |
2020-01-28 22:33:48 | eryksun | create | |
|