Skip to content
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
Merged

Update Python 2.7 EOL date #344

merged 1 commit into from Mar 14, 2018

Conversation

@hugovk
Copy link
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/

> 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
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@Mariatta
Copy link
Member

Mariatta commented Mar 14, 2018

Thanks!

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

debugtalk commented Mar 25, 2018

Cheers 😄

@maukoquiroga maukoquiroga mentioned this pull request Jul 24, 2018
7 of 8 tasks complete
webknjaz added a commit to cherrypy/cherrypy that referenced this pull request Mar 1, 2019
@nanonyme
Copy link

nanonyme commented Nov 30, 2019

Should the EOL day now be extended to the release day of the last maintenance release since as Guido's reasoning in the quote in original post there should be no support after EOL day?

@terryjreedy
Copy link
Member

terryjreedy commented Nov 30, 2019

No, release always happens sometimes after patching stops and the last 2.7 release was always going to happen some undefined time after EOL day. No one should expect any other support actions than release after 1/1/2020.

@hugovk
Copy link
Contributor Author

hugovk commented Nov 30, 2019

No, PEP 373 says of maintenance releases:

Being the last of the 2.x series, 2.7 will receive bugfix support until 2020. Support officially stops January 1 2020, but the final release will occur after that date.

Planned future release dates:

  • 2.7.18 code freeze January, 2020
  • 2.7.18 release candidate early April, 2020
  • 2.7.18 mid-April, 2020

https://www.python.org/dev/peps/pep-0373/#maintenance-releases

@nanonyme
Copy link

nanonyme commented Nov 30, 2019

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
Copy link
Member

tiran commented Nov 30, 2019

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.

@brouxco brouxco mentioned this pull request Apr 15, 2020
2 of 2 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

7 participants
You can’t perform that action at this time.