On 04-Oct-16 21:11, Zachary Ware wrote:
> Zachary Ware added the comment:
>
> Pip is a third party project, so if you'd like to pursue this please open an issue on the pip issue tracker at https://github.com/pypa/pip/issues.
I stand corrected.
> Anyway, pip installs links named the way it does so that you can be (more) sure that you're invoking the correct pip.  'pip3.6' will invoke the pip installed with python3.6, 'pip3' will (or at least should) invoke the pip installed with whatever 'python3' points to, and 'pip' will point to whatever 'python' points to.  When installed in a Python 3 venv, pip also installs a 'pip' link to 'pip3', just as there's also a 'python' link to 'python3'.  In 2.7, pip is also installed as 'pip2.7' and 'pip2' along with 'pip'; again mirroring the version tags on the interpreter links.
So, I guess I should rename my python-3.X packages python3-3.X so they 
can install side.by.side rather than only one or the other. Good point.
>
> ----------
> nosy: +zach.ware
> resolution:  -> third party
> stage:  -> resolved
> status: open -> closed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue28361>
> _______________________________________