Most likely, some will rename the command and some will not, causing more pain for everyone :(
I like using `<python_executable> -m pip` to avoid all ambiguity about what python version I'm running pip with/installing things for. Usually `python3 -m pip`, or `python3.8 -m pip`.
I like using pyenv to manage Python versions which will then always symlink "pip" and "python" to whichever version is my system default, directory tree default, shell default, virtualenv etc.
This is already the case. Arch has python for python 3 and python2 for python 2. It's the opposite on Ubuntu and most other distros.
Ubuntu 20.04 has python2 and python3 executables, but no python, so no ambiguity.
Re:Pip has dropped support for Python 2
by opheliate on Sunday January 24, 2021 @04:27AM
(#25890616)
This is absolutely my favourite way of doing it. If I need a `python` executable then I'll just make the symlink myself.
`sudo apt-get install python-is-python3` can fix that.
On Fedora:
$ python --version
Python 3.9.1
Re:Pip has dropped support for Python 2
by pseudalopex on Sunday January 24, 2021 @01:30AM
(#25889835)
Arch is why there's a PEP saying not to do that.
The PEP [0] has been revised since then, and the current recommendation regarding /usr/bin/python is "equivalent to python2 OR equivalent to python3 OR not available at all OR configurable by user/sysadmin".
This won't change that at all; pip/pip3 is a distro packaging thing, and any distro that packages legacy python2 as “python" and Python 3 as “python3” will probably continue packaging legacy pip-for-python2 as “pip” and pip-for-python3 as “pip3”.