On 19.09.2015 07:24, Stephen J. Turnbull wrote: > Barry Warsaw writes: > > > One thing that came up in a similar discussion is pip, and the > > suggested move to `python -m pip`, which makes a lot of sense. > > However, *inside* a virtualenv, there's no ambiguity about the > > Python version associated with direct `pip` invocation, so it still > > makes sense to install that there. > > And then the poor newbie who's just following orders (eg, in > mailman3/src/mailman/docs/INSTALL<wink/>) will try pip'ing outside of > the virtualenv for some reason, and have a WTF experience. I think we > should KISS the pip command good-bye. The only question I have: is there a particular reason (not technical one) why there are many pips on my PC? I would imagine 1 pip for the whole OS, that is capable to install packages inside arbitrary venvs AND handles different versions of Python. Best, Sven
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4