3 ms·
I do agree that if we see RHEL go to python3 as the default that would usher in major changes. However, Red Hat does not like to break backwards compatibility
by keypusher 12y ago
I do agree that if we see RHEL go to python3 as the default that would usher in major changes. However, Red Hat does not like to break backwards compatibility for its customers, and shipping python3 as the default would do that. This isn't an issue for Arch, as they do not rely on enterprise support contracts for their business model. However, this is part of the reason you don't see mission critical infrastructure running Arch. Also keep in mind that important operating system tools in rhel/fedora/etc rely on python, such as the yum package manager.
- johnny22 12y agoFedora 22 is/was switching the default package manager to dnf over yum. Fedora 23 should have Python 3 as default (although /usr/bin/python will still point to python 2.x) https://fedoraproject.org/wiki/Changes/Python_3_as_Default https://fedoraproject.org/wiki/Changes/Python_3_as_Default
- keypusher 12y agoInteresting. The page you linked actually seems to suggest they are removing /usr/bin/python or symlinking it to python3. It's part of the scope section. As far as I understand, whatever /usr/bin/python points to is "the default", so I'm not sure how you could switch "the default" and still have /usr/bin/python point to 2.x. So anyway, if Fedora goes to python3 in 2 years (23 release?) then it would probably be at least 5 years before we see RHEL pick up those changes, especially if it includes a change to the package manager and Anaconda (the os installer), both of which are central to RHEL. My guess is that Red Hat are going to be very careful pulling these changes in for enterprise.