[Python-Dev] Proposing the deprecation of the pyvenv script (original) (raw)
Sven R. Kunze srkunze at mail.de
Sat Sep 19 11:12:52 CEST 2015
- Previous message (by thread): [Python-Dev] Proposing the deprecation of the pyvenv script
- Next message (by thread): [Python-Dev] Proposing the deprecation of the pyvenv script
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 directpip
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) 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
- Previous message (by thread): [Python-Dev] Proposing the deprecation of the pyvenv script
- Next message (by thread): [Python-Dev] Proposing the deprecation of the pyvenv script
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]