➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2016-10-04 18:46 by Michael.Felt, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Messages (4) | |||
|---|---|---|---|
| msg278075 - (view) | Author: Michael Felt (Michael.Felt) * | Date: 2016-10-04 18:46 | |
a) pip is embedded in Python for some time. b) pip is called pip3.5 (with link to pip3) c) in Python3.6 pip is now called pip3.6 and linked to pip3 pip is pip - not pip3* because python is now called python3* pip is pip - currently version 8.1.2 - what does that have to do with pip3? IMHO - the name should just be pip p.s. in Python2.7 - pip is embedded, but not installed automatically. However, when you run the embedded install - pip is pip |
|||
| msg278081 - (view) | Author: Zachary Ware (zach.ware) *  |
Date: 2016-10-04 19:11 | |
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. 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. |
|||
| msg278097 - (view) | Author: R. David Murray (r.david.murray) * |
Date: 2016-10-05 00:30 | |
There's really not much point in opening an issue in the pip tracker; this is working as designed, as Zach explained. On posix you "shouldn't" be using pip outside of a virtual environment anyway :) |
|||
| msg278151 - (view) | Author: Michael Felt (aixtools@gmail.com) | Date: 2016-10-05 21:20 | |
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> > _______________________________________ |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:37 | admin | set | github: 72547 |
| 2016-10-05 21:20:06 | aixtools@gmail.com | set | nosy:
+ aixtools@gmail.com messages: + msg278151 |
| 2016-10-05 00:30:03 | r.david.murray | set | nosy:
+ r.david.murray messages: + msg278097 |
| 2016-10-04 19:11:43 | zach.ware | set | status: open -> closed nosy: + zach.ware messages: + msg278081 resolution: third party stage: resolved |
| 2016-10-04 18:46:02 | Michael.Felt | create | |