On Wed, 11 Nov 2015 at 04:06 Paul Moore <p.f.mo...@gmail.com> wrote: > On 11 November 2015 at 06:35, Nick Coghlan <ncogh...@gmail.com> wrote: > > Windows Python 2 installations require manual PATH modifications > > regardless, but it's more common for people to know how to make > > "python -m pip install X" work, than it is for them to remember to > > also add the "Scripts" directory needed to make "pip install X" work. > > ... and "py -m pip install X" works without any PATH modification on > all Windows systems with the launcher installed (I can't recall if > it's included with Python 2.7 - but if not, maybe it should be > backported? There's a standalone version people can get as well). >
While the discussion to try and get UNIX to adopt `py` is nice, I think that decision falls under python-dev's jurisdiction. So if people here decide "we should be pushing for that" then that's great, but that means someone needs to go to python-dev and say "distutils-sig is trying to solve the issue of `pip` being ambiguous as to what Python installation it works with and we thought making `py` a thing on UNIX was the best solution forward for `py -m pip`". And if that's the case then the stop-gap is `python -m pip`.
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
