On Sat, Nov 7, 2015, 5:41 PM 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. I've actually stopped using "pip install" in favor of "python -m pip install" for this very reason. At the very least I know that if my next command is "python <something>" I'll have those packages installed in that same python. On windows I used "py -3.4 -m pip". -W
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
