Forum Archive

Inspired by https://pythonclock.org

Just to help you convince your bosses that porting to Python 3 must be completed soon.

https://github.com/cclauss/Ten-lines-or-less/blob/master/daze_left.py currently says:

• 627 days until Python 2 end of life.
• On 2018-05-11 there will be 600 days until Python 2 end of life.
• On 2018-08-19 there will be 500 days until Python 2 end of life.
• On 2019-04-26 there will be 250 days until Python 2 end of life.
• On 2019-09-23 there will be 100 days until Python 2 end of life.

100 days until Python 2 end of life. https://www.python.org/doc/sunset-python-2

Please define “end of life”. Does it mean that on that date all Python 2 interpreters will stop working? Will operating systems worldwide delete Python 2 and all its libraries from their environment? Will the dead Python 2 be erased from the universal consciousness of humankind and spying invisible aliens?

@Ti-Leyon https://en.wikipedia.org/wiki/End-of-life_(product)

@Ti-Leyon, as a concrete impact: ”Django 1.11 is the last version to support Python 2.7. Support for Python 2.7 and Django 1.11 ends in 2020.”

@Ti-Leyon Actually, any devices still running python2.7 will instantly explode, into flames, possibly ending your life. The PSF does NOT mess around.

Thank you for the link @dgelessus but I just wanted to point out that in a technical environment we should probably talk about “end of support” instead of “end of life”. What about basic idea shaping @mikael? Fundamental research can be tested in any language even “dead” ones. However, Python beats them all with out of the box arbitrary length integers for certain problems. In fact I just got a breakthrough factorizing large semi-primes using Python 2. When (and if) I release its source, I will make sure to set it to be incompatible with 3.x forcing “modern” users to make corrections in every lines or use Python 2. Well @JonB you are right so we better be careful with that “dangerous” Python 2. I wonder if those, like me, who still will use it after the “end of life” deadline will turn into “ghost programmers”. Anyway, thank you all for sharing the humor.

EOL is what the Python Core Team calls it https://devguide.python.org/devcycle/#end-of-life-branches
vs. https://devguide.python.org/#branchstatus

BTW, PyPy (the python JIT which is in many usecases faster than CPython) will continue to support py2 indefinetly and probably forever. So as long as you do not have to use c-dependent modules and are OK with using outdated modules, it is a good way to continue using py2 after its EOL.

Daze_left = None!!

Thanks for the reminder but I will be using dead Python 2 for many fruitful years to come. Happy New Year!