classification
Title: Should `make install` still install to /usr/bin/python3?
Type: enhancement Stage: resolved
Components: Installation Versions:
process
Status: closed Resolution: postponed
Dependencies: Superseder:
Assigned To: Nosy List: eamanu, eric.smith, pxeger
Priority: normal Keywords:

Created on 2020-10-10 12:21 by pxeger, last changed 2020-10-10 12:44 by eric.smith. This issue is now closed.

Messages (3)
msg378387 - (view) Author: Patrick Reader (pxeger) * Date: 2020-10-10 12:21
Since Python 2 is now finally gone, should the Python executable not be installed to simply `/usr/bin/python` rather than `/usr/bin/python3` when running `make install`?
msg378388 - (view) Author: Emmanuel Arias (eamanu) * Date: 2020-10-10 12:37
Hi,

There're many people that still use py2, or both.
Also python2 (python) is incompatible with python3, so we cannot
call python == python3.

(There was some discussion on Debian, just if you want take a look
https://lists.debian.org/debian-python/2020/07/msg00042.html)
msg378390 - (view) Author: Eric V. Smith (eric.smith) * (Python committer) Date: 2020-10-10 12:44
There's a PEP for this: PEP 394. If you want to change this, I suggest discussing it on the python-dev mailing list. If that leads to changes in the PEP, this issue can be re-opened.

Personally I don't see this change happening until there are no systems left that install python2 as /usr/bin/python. Which is unfortunate, but such is life. Myself, I have a shell alias for python that points to python3. That solves 95% of my problems.
History
Date User Action Args
2020-10-10 12:44:47eric.smithsetstatus: open -> closed

nosy: + eric.smith
messages: + msg378390

resolution: postponed
stage: resolved
2020-10-10 12:37:38eamanusetnosy: + eamanu
messages: + msg378388
2020-10-10 12:21:05pxegercreate