On Mon, 9 Nov 2015 11:16:56 +0000 Oscar Benjamin <oscar.j.benja...@gmail.com> wrote: > On 9 November 2015 at 10:44, Wolfgang Maier > <wolfgang.ma...@biologie.uni-freiburg.de> wrote: > > > > Something I miss in all the discussions taking place here is the fact that > > python -m pip is the officially documented way of invoking pip at > > https://docs.python.org/3/installing/index.html#basic-usage and it is not > > particularly helpful if that recommendation keeps changing back and forth. > > > > I know some people don't like the wordy invocation, but other people > > (including me) use and teach it because it works reliably. Just because a > > pip executable based invocation pattern looks better, I don't think it > > justifies the change. > > I also teach this invocation. Somehow you have to select the Python > version you're interested in and I really don't see why
"Selecting the Python version you're interested in", in many cases, is done /a priori/ by activating the appropriate environment (whether virtualenv-, pyvenv- or conda-based). When I'm using a conda environment I certainly don't want to type "python -m pip" when "pip" is sufficient. It would be nice if people here could acknowledge the diversity of existing workflows. Regards Antoine. _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig