> Python 2 is no longer installed by default. Python 3 has been updated to 3.6.
And so it begins. I think/hope that the next RHEL will do the same thing, at which point the final nail will be in Py2's coffin.
And so it begins. I think/hope that the next RHEL will do the same thing, at which point the final nail will be in Py2's coffin.
https://developers.redhat.com/blog/2014/09/17/why-python-4-0...
If you like python3, great for you. But why do you want to kill python2 if other people are happy with it?
I offer no opinion whatsoever on which is better, only that it’s probably better for everyone if dev efforts are not split between two versions of the same language.
You can make the same argument for any software suite which moves over time. Why should Firefox 10 die, just because Firefox 57 is out in a month or so?
Well.. Duh. The new code has to live somewhere, and we don't want to spend eternity backporting fixes to the old codebase.
Please do note: You can still use Python 2 if you like. But if you rely on really old and antiquated technology, you can't expected modern OSes to ship it by default. Now it becomes your liability to instruct your users in how to obtain your antiquated dependencies for your software to work.
Maybe that is a good enough solution, or maybe some day you will find that it's more beneficial to move along with the rest of the ecosystem.
Nobody writes new code in Python 2 any more. It's the programming language equivalent of Windows XP at this point.
Still true of course that it doesn't have to be installed by default even if some applications still need it.
Tell that to Arch. :(
But it seems that they have a v2 in the works that's supposed to support Python3: https://github.com/fabric/fabric/tree/v2
And there's also a fork: https://pypi.python.org/pypi/Fabric3
I'm not familiar with the details, but does this mean that they're resisting patches to support 3.x? Given the existence of a fork it seems likely. It's not-at-all difficult to write a single Python package that works on both 2.7 and 3.x. Especially if you are willing to use `six`.
I'll admit that it's a little harder to stay compatible with earlier-than-2.7, though.
I think the actual argument against Py3-compatibility is exactly that: Fabric needs to support 2.6 because it is the default in RHEL/SLES versions which are still quite popular in enterprise environments and maintaining compatibility with both Py 2.6 and Py 3 is quite difficult, as you said.
I would be surprised if they didn’t give any overlap between 2 and 3 in RHEL 8.