https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109668
Bug ID: 109668
Summary: 'python' vs. 'python3'
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
Target Milestone: ---
In GCC sources, there exist a number of Python scripts that invoke 'python'
(for example, 'contrib/dg-extract-results.sh'), or '/usr/bin/python' (for
example, 'contrib/dg-extract-results.py').
Now, in my new Ubuntu 22.04 "jammy" installation, '/usr/bin/python' doesn't
exist anymore, but only '/usr/bin/python3'.
Do we intend to adjust all GCC's Python scripts to handle this scenario in some
generic way, or do we continue to require 'python' for GCC?
The latter may, for example, be achieved with Debian/Ubuntu package
python-is-python3:
[...]
Description: symlinks /usr/bin/python to python3
Starting with the Debian 11 (bullseye) and Ubuntu 20.04 LTS (focal)
releases, all python packages use explicit python3 or python2
interpreter and do not use unversioned /usr/bin/python at all. Some
third-party code is now predominantly python3 based, yet may use
/usr/bin/python.
[...]
Conversely, the already exist a number of explicitly 'python3' instances in GCC
sources, too.
---
I noticed this via the shell version 'contrib/dg-extract-results.sh' producing
different results than the Python version 'contrib/dg-extract-results.py' that
I had been using before (via 'contrib/dg-extract-results.sh' invoking it), but
no longer due to no 'python' executable being available anymore.
