New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Python 2.7 EOL date #344

Merged
merged 1 commit into from Mar 14, 2018

Conversation

Projects
None yet
4 participants
@hugovk
Contributor

hugovk commented Mar 14, 2018

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/

Update Python 2.7 EOL date
> 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/

@terryjreedy terryjreedy requested review from benjaminp and Mariatta Mar 14, 2018

@Mariatta Mariatta merged commit fc40015 into python:master Mar 14, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
@Mariatta

This comment has been minimized.

Member

Mariatta commented Mar 14, 2018

Thanks!

@hugovk hugovk deleted the hugovk:patch-1 branch Mar 14, 2018

@debugtalk

This comment has been minimized.

debugtalk commented Mar 25, 2018

Cheers 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment