[StRoy]

> Of course you can continue using Python 2.x after 2020 but you will receive no security/bug fixes.

I keep seeing this irrelevant line all the time from Python 3 Ayatollah and High Priests. Python 2 isn't only CPython. So what if the Python foundation stops maintaining CPython? Dropbox is writing a new, efficient Python 2 implementation to make their legacy Python programs run faster while they slowly port to Go.

There's Pyston, there's PyPy, there's Jython, there's IronPython. We don't depend on CPython security fixes thank you very much. And so far none of them have made an EOL announcement of their Python 2 releases, while in the case of Pyston, being Python 2 is a must, dropbox is never going to port anything to Python 3. If something is worth wasting time with Python 3, it's worth rewriting in Go.

[aaronbasssett]

Pyston, Jython, IronPython; they're all esoteric when compared to CPython. And while Pyston or similar may continue their own Python 2 implementation many library/package authors will simply not support it. So your interpreter may not be EOL'd but you'll very quickly find the package versions you rely upon will be.