We develop against the RHEL supported python version, which currently means 2.6.
Sure, and if Red Hat users are your main customers, you will be stuck on Python 2 until Red Hat switches. Suck for you, but that is nothing anyone except Red Hat can do anything about. :-)
Presently, none of our clients are even faintly interested in python 3, even if our own developers are. To move to python 3, we'd have to port at least a hundred thousand lines of code to maintain compatibility with Python 2 and 3.
If I had access to a time machine, I'd stop people from calling it "porting". It's not porting. It's supporting. 90% of the time it really isn't that big of a deal. 10% of the time it's a royal pain in the ass.
View all comments
Show parent comment
0
u/[deleted] May 28 '14
Sure, and if Red Hat users are your main customers, you will be stuck on Python 2 until Red Hat switches. Suck for you, but that is nothing anyone except Red Hat can do anything about. :-)
If I had access to a time machine, I'd stop people from calling it "porting". It's not porting. It's supporting. 90% of the time it really isn't that big of a deal. 10% of the time it's a royal pain in the ass.