Hi, My perspective as a user of pip, but not a developer, is that having the command line executable `pip` is much preferable to `python -m pip`. Most of the use cases that militate against the command line executable seem to be issues that face developers and ultra-power-users (keeping track of many versions of pip installed, etc). But many casual users, I think, just have one version of python/pip installed, and benefit from having the easy-to-call executable. They're also the least capable of adding new script wrappers and bash aliases.
Just my $0.02 Best, -Robert On Thu, Nov 5, 2015 at 6:49 PM, Glyph Lefkowitz <[email protected]> wrote: > > On Nov 5, 2015, at 5:04 PM, Robert Collins <[email protected]> > wrote: > > cat > /usr/bin/pip << EOF > python -m pip $@ > EOF > > Seriously - isn't the above entirely sufficient? > > > Since I don't think anyone has pointed this out yet: > > No, it's not sufficient. It doesn't work on Windows. > > -glyph > > > _______________________________________________ > Distutils-SIG maillist - [email protected] > https://mail.python.org/mailman/listinfo/distutils-sig > >
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
