What, no Python in Red Hat Enterprise Linux 8?
TL;DR Of course we have Python! You just need to specify whether you want Python 3 or 2 as we didn’t want to set a default. Give
yum install python3 and/or
yum install python2 a try. Or, if you want to see what packages we recommend, use
yum install @python36 or
yum install @python27. Read on for why.
For prior versions of Red Hat Enterprise Linux, and most Linux distributions, users have been locked to the system version of Python unless they got away from the system’s package manager. Although this can be true for a lot of tools (Ruby, Node, Perl, PHP), the Python use case is more complicated because so many Linux tools (like yum) rely on Python. To improve the experience for Red Hat Enterprise Linux 8 users, we have moved the Python used by the system “off to the side” and introduced the concept of Application Streams based on Modularity.
Through Application Streams, in combination with Python’s ability to be parallel installed, we can now make multiple versions of Python available and easily installable, from the standard repositories, into the standard locations. No extra things to learn or manage. Now, users can choose what version of Python they want to run in any given userspace and it simply works. For more info, see Introducing Application Streams in RHEL 8.
To be honest, the system maintainers also get some advantages of not being locked to an aging version of Python for our system tools. With users not relying on a particular version of Python coming with the system installation, we have the freedom to take advantage of new language features, performance improvements, and all the other goodness a developer gets when tracking near the upstream version.
However, this has resulted in a dilemma. When a user sits down at a fresh installation of Red Hat Enterprise Linux 8, they will naturally expect that
/usr/bin/pythonwill run some version of Python. If you follow the recommendation in Python Enhancement Proposal (PEP) 394, that will be Python 2. However, at some point, a new PEP will likely want to change that recommendation to Python 3, probably during the typically *10* year life of Red Hat Enterprise Linux 8. To put this in perspective, consider that Red Hat Enterprise Linux 7 was released in 2014, and will be supported until 2024!
So, what do we do? Well, if we follow the current recommendation, we make some present-day users happy. However, when the Python community shifts to recommending Python 3 as the default, we will make new users unhappy.
As a result, we came to the tough conclusion: don’t provide a default, unversioned Python at all. Ideally, people will get used to explicitly typing
python2. However, those that want an unversioned command can choose from the beginning which version of Python they actually want. So,
yum install python results in a 404.
However, we do try to make it as easy as possible to get Python 2 or 3 (or both) on to your system. We recommend using
yum install @python36or
yum install @python27 to take advantage of the recommended set of packages to install. If all you really need is *just* the Python binaries, you can use
yum install python3 or
yum install python2.
We have also set up the alternatives infrastructure so that when you install either (or both) you can easily make
/usr/bin/python point to the right place using
alternatives --config python. However, as we explained above, and aligned with the Python PEP, we don’t recommend relying on
/usr/bin/python being the correct Python for your application.
Note: the same issue arises for Python wrapper scripts like
pip. Installing Python 3 will put
pip3 in your path, but not unversioned
pip. With Python modules like
virtualenv, you can avoid confusion and get the right version by running those as a module:
python3 -m pip and avoiding the wrapper scripts. Using Python virtual environments is a best practice that also avoids the issues with version ambiguity, see How to install Python 3 on Red Hat Enterprise Linux 7 for virtual environment details and advice.
To conclude, yes, Python is included in Red Hat Enterprise Linux 8. And, it will be even better than in the past. If you want more details, refer to the How To Guide on Red Hat Developers.
And if you haven’t downloaded Red Hat Enterprise Linux 8 yet, go to developers.redhat.com/rhel8 now.
Everything you need to grow your career.
With your free Red Hat Developer program membership, unlock our library of cheat sheets and ebooks on next-generation application development.SIGN UP
- Red Hat Enterprise Linux 8 for developers
- Introducing Application Streams in RHEL 8
- Petr Viktorin’s Python on RHEL 8 article (see the discussion of Platform Python)
- Introducing CodeReady Linux Builder
- Containers without daemons: Podman and Buildah available in RHEL 7.6 and RHEL 8 Beta
Take advantage of your Red Hat Developers membership and download RHEL today at no cost.