4 ms·
It's not even python2.7, they went with 2.6. A version that reached end of official support in 2013. All because that's the default for RHEL 6. It's not hard t
by onei 6y ago
It's not even python2.7, they went with 2.6. A version that reached end of official support in 2013. All because that's the default for RHEL 6.
It's not hard to build RPMs of newer and/or supported versions of Python. You might even find it in EPEL. I get being risk averse, but if you're going to make the change, move to something sensible that your developers will want to work with.
- throwaway8941 6y agoNo need to build anything. https://www.softwarecollections.org/en/ https://www.softwarecollections.org/en/
- ChrisSD 6y agoOn the other hand Python 2.6 will be supported on RHEL 6 for as long as RHEL 6 is supported. Of course this still means having to switch again in a few years time but that's a problem for future JP Morgan.
- bdavis__ 6y agoCentos6 goes out of support this year.
- ChrisSD 6y agoSure but RHEL 6 has Extended Life-cycle Support until 2024.
- tyingq 6y agoRHEL 6 EOL is 11/30/2020. There's "extended support", but no patches, not even security patches. Edit: Apparently I was wrong about some security patches, but ELS sounds complicated: https://access.redhat.com/discussions/2399461 https://access.redhat.com/discussions/2399461
- user5994461 6y ago>>> It's not hard to build RPMs of newer and/or supported versions of Python. It's actually the hardest thing to do and to maintain long term. I'd say from experience that building your own is the #1 thing that was plaguing legacy systems in the bank and preventing to maintain them. Developers built perl/python/whatever manually and distributed (RPM or whatever). It's de facto unmaintainable because it cannot be built again. Sure thing is, there were special build flags set and some extra libraries/plugins embedded into the build, but who knows? There is never any instruction left. Even if there was, these are complex software with huge web of dependencies, it's probably impossible to get everything to run/build 5-10 years later. (DLL hell is a major recurrent issue on Linux when upgrading the distro and some old libraries are gone due to googlecode/sourceforge dying). Hence the solution to ensure that simple critical scripts work and can be maintained in the far future when required, is to rely on the /usr/bin/python from RHEL (and store everything in source control). Don't build your own interpreter.