Re:Where are we in the Python 3 transition?
by kemayo on Friday January 01, 2016 @05:29PM
(#10823798)
It's just the author pointing out that the EOL for official support for Python 2 is 2020. After then, the Python dev team won't be providing any (free) support, so people who want to keep using it will have to pay for it in some way -- whether by investing time in maintaining a fork, or by paying someone else to do so.
The absence of a "Python 2.8" fork suggests that the idea of forking hasn't been popular enough to happen organically without someone putting money in, after all.
Re:Where are we in the Python 3 transition?
by someguydave on Saturday January 02, 2016 @02:59PM
(#10827621)
>The absence of a "Python 2.8" fork suggests that the idea of forking hasn't been popular enough to happen organically without someone putting money in, after all.
Or it's evidence that python 2.7 works just fine for many people.
Re:Where are we in the Python 3 transition?
by Ded7xSEoPKYNsDd on Friday January 01, 2016 @07:01PM
(#10824235)
Cent OS 7 will support Python 2 for free until 2024. I would assume most patches will work without changes on other OSes as well. But if you want someone to do the QA work (and compiling) for you and no independent Python 2 fork will arise, you'd presumably have to pay someone for that.
Beyond that, apparently you can pay Red Hat to big bucks to provide you with bug fixes for really old Red Hat releases in a similar way you can pay Microsoft big bucks to get patches for Windows XP even today. I'm sure other companies will do the same if they can find enough customers that find porting costs more than such a support contract.
Is this some sort of thing?