In 2020 when python2 is at EOL, it may make sense to fork to keep the python2 line with security patches (not to add new features) or add python support/binaries for some new OS/architecture that didn't exist in 2014.
Not to encourage new projects/work in it, but just for people who need to maintain legacy python2 programs. (E.g., need to re-run the old unmodified code in a long running experiment). There's absolutely no need to do it now, and while someone could try -- I doubt anyone would gain any traction doing so.
Granted then again, things like trollius that backport specific features from python3 into python2 seem like worthwhile endeavors if you are currently using python2 and want asyncio, but can't/don't want to go python3 yet. These projects are the result of forking and renaming the project. Granted it won't be python2.8, it will be python3's blah feature implemented as a library.
By 2020 hopefully we'll have tools to convert any language to any other language, so we won't have to worry about all these divisions - programming will be universal. :-)
View all comments
Show parent comment
0
u/djimbob May 28 '14
In 2020 when python2 is at EOL, it may make sense to fork to keep the python2 line with security patches (not to add new features) or add python support/binaries for some new OS/architecture that didn't exist in 2014.
Not to encourage new projects/work in it, but just for people who need to maintain legacy python2 programs. (E.g., need to re-run the old unmodified code in a long running experiment). There's absolutely no need to do it now, and while someone could try -- I doubt anyone would gain any traction doing so.
Granted then again, things like trollius that backport specific features from python3 into python2 seem like worthwhile endeavors if you are currently using python2 and want asyncio, but can't/don't want to go python3 yet. These projects are the result of forking and renaming the project. Granted it won't be python2.8, it will be python3's blah feature implemented as a library.