Brian C. Lane wrote:
I'm opposed to this change. I see no reason to complicate things
because
some other distributions (Arch) have inadvisedly redirected
/usr/bin/python to python3. This whole mess violates the principle of
least surprise -- as a user of python what do you expect
/usr/bin/pythong to do? You expect it to run the python2 interpreter.
Any 3rd party programs that users install will also expect this, so this
change will cause their applications to fail.
I think the rules can be distilled down to this:
* New python2 programs use /usr/bin/python2
* New python3 programs use /usr/bin/python3
* Leave /usr/bin/python pointing to /usr/bin/python2 for legacy
programs
There is no good reason to make this change. Leaving it as it is now
doesn't break anything.
+1. We should just stop doing pointless incompatible changes. All programs
using Python 2 are legacy programs. So just let them use the legacy names
forever. New programs use /usr/bin/python3.
Even if, as this feature proposes, the change is made only for RPM builds,
that still means a lot of pointless work for packagers of legacy upstream
software that will never be updated to use /usr/bin/python2, let alone
ported to Python 3.
The Chromium build scripts used during QtWebEngine builds are full of
"#!/usr/bin/env python" shebangs. A lot have not been touched since 2012.
Remove /usr/bin/python and QtWebEngine will no longer build.
Kevin Kofler