Revision history [back]

The problem comes from the fact that in Debian-related distros, python command was refering to the Python 2 interpreter and python3 was used for Python 3. Now that Python 2 disapeared, there is no command named python anymore, and it is not so bad that redirecting this command to Python 3 interpreter is not automatic (at least for now).

The simplest way to let the command python run Python 3 interpreter is to install the package python-is-python3, which basically just adds a symlink /usr/bin/python -> /usr/bin/python3.

The problem comes from the fact that in Debian-related distros, python command was refering to the Python 2 interpreter and python3 was used for Python 3. Now that Python 2 disapeared, there is no command named python anymore, and it is not so bad that redirecting this command to Python 3 interpreter is not automatic (at least for now).now), to avoid confusions with scripts relying on Python 2, and also because it is still possible to install Python 2 interpreter.

The simplest way to let the command python run Python 3 interpreter is to install the package python-is-python3, which basically just adds a symlink /usr/bin/python -> /usr/bin/python3.

The problem comes from the fact that in Debian-related distros, python command was refering to the Python 2 interpreter and python3 was used for Python 3. Now that Python 2 disapeared, there is no command named python anymore, and it is not so bad that redirecting this command to Python 3 interpreter is not automatic (at least for now), to avoid confusions with scripts relying on Python 2, and also because it is still possible to install Python 2 interpreter.

The simplest way to let the command python run Python 3 interpreter is to install the package python-is-python3, :

sudo apt install python-is-python3

which basically just adds a symlink /usr/bin/python -> /usr/bin/python3.