On Tue, Jul 27, 2021 at 2:04 PM Neal Gompa <ngompa13@gmail.com> wrote:
On Tue, Jul 27, 2021 at 5:09 AM Tomas Orsava <torsava@redhat.com> wrote:
>
> If I understand what you're describing correctly, this is not a bug.
> In the default state, /usr/bin/python should *not* exist, that's correct behaviour. If you want it to exist, you need to configure it using alternatives [0].
>
> We considered making /usr/bin/python exist but be a noop, but that breaks a lot of automated (build) tools that search for Python executables (they often start with python, if not found search for python3, or python2, etc.).
> And there was no reasonable default for Python in RHEL 8 because it sits between the past (Python 2 default in RHEL 7) and the future (Python3 default in RHEL 9). Either default would cause problems, often hidden and hard to debug problems, for some subset of our customers.
>
> [0] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/assembly_configuring-the-unversioned-python_configuring-basic-system-settings
>

But this won't be a problem in RHEL 9, will it? I don't want to suffer
through this when we're not even going to have Python 2 in RHEL 9 at
all...

It will not be a problem in RHEL9.  I just verified and  it is setup like Fedora

[root@cs9 ~]# which python
/usr/bin/python
[root@cs9 ~]# rpm -qf /usr/bin/python
python-unversioned-command-3.9.5-3.el9.noarch
[root@cs9 ~]# dnf provides '/usr/bin/python'
python-unversioned-command-3.9.6-1.el9.noarch : The "python" command that runs Python 3
Repo        : cs9-appstream
Matched from:
Filename    : /usr/bin/python