On Sat, 7 Nov 2015 23:41:25 +0000 Paul Moore <p.f.mo...@gmail.com> wrote: > On 7 November 2015 at 22:21, Antoine Pitrou <solip...@pitrou.net> wrote: > > The actual question is: which problem are you trying to solve *that > > current users are actually experiencing*? > > Typically, people using "pip" to install stuff, and finding it gets > installed into the "wrong" Python installation (i.e., not the one they > expected). I'm not clear myself on how this happens, but it seems to > be common on some Linux distros (and I think on OSX as well) where > system and user-installed Pythons get confused.
Well, the problem is that "python -m pip" isn't any better. If you don't know what the current "pip" is, then chances are you don't know what the current "python" is, either. (I'm not trying to deny the issue, I sometimes wonder what "pip" will install into exactly, but removing the command in favour of a "-m" switch wouldn't do any any good IMO, and it would make Python package management "even more baroque" than it currently is) Regarrds Antoine. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
