Update Python 2.7 EOL date

[hugovk]

Let's not play games with semantics. The way I see the situation for 2.7 is
that EOL is January 1st, 2020, and there will be no updates, not even
source-only security patches, after that date. Support (from the core devs,
the PSF, and python.org) stops completely on that date. If you want support
for 2.7 beyond that day you will have to pay a commercial vendor. Of course
it's open source so people are also welcome to fork it. But the core devs
have toiled long enough, and the 2020 EOL date (an extension from the
originally annouced 2015 EOL!) was announced with sufficient lead time and
fanfare that I don't feel bad about stopping to support it at all.

Guido van Rossum, https://mail.python.org/pipermail/python-dev/2018-March/152348.html

Sounds good to me. I've updated the PEP to say 2.7 is completely dead on Jan 1 2020. The final release may not literally be on January 1st, but we certainly don't want to support 2.7 through all of 2020.

Benjamin Peterson, https://mail.python.org/pipermail/python-dev/2018-March/152355.html

Being the last of the 2.x series, 2.7 will have an extended period of maintenance. Specifically, 2.7 will receive bugfix support until January 1, 2020. All 2.7 development work will cease in 2020.

Benjamin Peterson, https://www.python.org/dev/peps/pep-0373/

[Mariatta]

Thanks!

[debugtalk]

Cheers 😄

[nanonyme]

Do you mean codebase is actually hard frozen in January on the level that no fixes before maintenance release goes out are allowed? Because otherwise it means Python 2 is supported almost half of 2020 with or without EOL.

[tiran]

Support for Python 2 by Python core development ends by the end of the year. There will be no support by us in 2020. Benjamin (release manager for Python 2.7) decided to postpone the last release until PyCon US in April 2020.