That's incredibly naïve. Python 2 will be around and have new software written with it for at least a decade to come. Keep saying "Python 3 is the future", that will surely make companies invest in switching. Meanwhile ford still uses 40 year old IBM mainframes with COBOL, and will continue to do so until they are physically unable.
Re:Python 2.7 Retirement Countdown
by cookiecaper on Saturday May 28, 2016 @09:11PM
(#11794334)
As others posters have commented, Python 2 will survive in the sense that there will always be some code running on it (and there will be a niche market for dark artists who can massage it). Python 2 will not survive in the sense that no one will be writing new code for it. Python 3 is already commonly used for new projects and it's scheduled to get several big boosts in that direction as Ubuntu and Fedora switch to it as the default Python.
The old meme that it's unsafe to use Py3 is not true anymore. Practically all of the big libraries work fine on Python 3 now. Py3 code is going to be dominant in new projects in short order if it isn't already, and it's plausible that new Py2 projects will be virtually extinct by 2020.
Re:Python 2.7 Retirement Countdown
by asdfologist on Saturday May 28, 2016 @08:48PM
(#11794275)
You've just proved his point by comparing Python 2 with 40 year old mainframes. There will always be users of legacy software, but that doesn't stop it from being, well, legacy software.
Re:Python 2.7 Retirement Countdown
by Bromskloss on Sunday May 29, 2016 @04:57AM
(#11795576)
> ford still uses 40 year old IBM mainframes with COBOL,
What are they using it for?
I would be so happy if our company could migrate everything to Python 2.7. We still have a lot of 2.5 and 2.6 around.
Also, "supporting legacy code for money" is already everyone's job, unless you're implying that there are as many Python programmers as there are COBOL ones.