Author eryksun
Recipients Jeff.Edwards, brett.cannon, eryksun, vinay.sajip
Date 2020-01-28.22:33:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> 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 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:49eryksunsetrecipients: + eryksun, brett.cannon, vinay.sajip, Jeff.Edwards
2020-01-28 22:33:48eryksunsetmessageid: <>
2020-01-28 22:33:48eryksunlinkissue39469 messages
2020-01-28 22:33:48eryksuncreate