https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109668
Paul Iannetta <piannetta at kalrayinc dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |piannetta at kalrayinc dot com --- Comment #2 from Paul Iannetta <piannetta at kalrayinc dot com> --- My first guess was that unless GCC made clear that it will requires Python3, I thought that all the Python scripts should be kept compatible with both Python2 and Python3. However, looking at GCC sources, most python files already require python3 in their shebang (#!/usr/bin/env python3), which would suggest that we can safely drop python2 and use python3 everywhere, and rewrite the few #!/usr/bin/python3 to #!/usr/bin/env python3 % find gcc/ -iname "*.py" -exec head -n 1 '{}' + | grep "python$" -C 1 ==> ./libstdc++-v3/scripts/make_graph.py <== #!/usr/bin/python ==> ./libffi/generate-darwin-source-and-headers.py <== #!/usr/bin/env python ==> ./contrib/jit-coverage-report.py <== #! /usr/bin/python ==> ./contrib/dg-extract-results.py <== #!/usr/bin/python ==> ./contrib/unused_functions.py <== #!/usr/bin/env python