On 14 November 2017 at 11:51, Nathaniel Smith
What if instead of installing a standard entry point, the pip executable was installed as
#!/bin/sh exec python -m pip "$@"
on Unix-likes
It would technically be enough to make the shebang line `#!/usr/bin/env python` so the interpreter used was picked up from the environment, rather than being preconfigured at install time. However, the problem is that you don't know for certain that that python will actually have `pip` installed, so it might just fail with a cryptic error instead. However, `pip` could potentially be updated with a `checkenv` subcommand that complains if `sys.executable` and `shutil.which('python')` don't match (and could presumably include other checks as well).
and a pip.bat with the equivalent contents on Windows? (Bonus: maybe this would fix the problem with upgrading pip on Windows?)
Depending on how the batch file was written, I think the answer to that is "maybe": https://stackoverflow.com/questions/2888976/how-to-make-bat-file-delete-it-s... Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia