On 24/09/2019 04:21:45, Benjamin Peterson wrote:
On Fri, Sep 13, 2019, at 18:18, Sumana Harihareswara wrote:
Hi. I've joined python-dev to participate in this thread (I don't have email delivery turned on; I'll be checking back via the web).
Benjamin, I am sorry that I didn't check in with you, and assumed that January 1, 2020 would be the the date of the final 2.7 point release. (My understanding was based on Guido's EOL announcement from March last year https://mail.python.org/pipermail/python-dev/2018-March/152348.html -- I should have also gotten a review from you and not just the Steering Council in https://github.com/python/steering-council/issues/14 .) I'm going to continue this discussion here so I can make sure I understand the policy decision properly, and then (if necessary) update the FAQ.
Based on what I've read here and what I see in https://www.python.org/dev/peps/pep-0373/#maintenance-releases , it sounds like the timeline will go something like:
- 2019-10-19: release of 2.7.17 October
- October, November, and December 2019: developers continue to fix
issues in 2.7
- 2020-01-01: code freeze for 2.7.18 release candidate
- January and February 2020: flexibility to fix any issues introduced
since the 2.7.17 release, but no other bugs or security issues, and no 3.x backports
Security issues will probably be fixed. At least, I wouldn't in abstract find that objectionable assuming someone wants to write a patch.
- ~2020-04-02: release candidate for 2.7.18
- 2020-04-17: final 2.7.18 release
I don't know if these will be the exact dates but probably close.
Is this right? (If so, I can submit an update to PEP 373.)
This is a little more complicated than I had anticipated when communicating out about the sunsetting. But I can find a way either to concisely communicate this, or to point to a user-friendly explanation elsewhere.
A succinct statement of the relevant information is: "After 10 years, the core developers of CPython are stopping development on the 2.7.x line. The last release will be in April 2020." If it's easier to communicate that the sunset of CPython 2 is April 2020, that seems fine with me.
January 1 was a somewhat arbitrary date we put in the PEP when 2020 still seemed like a long way off but people wanted to know whether 2.7 would be released until 2021 or not. I was never going to make a 2.7 release literally on January 1. (Fighting with GPG would make short work of New Year's resolutions pertaining to temperance and strong language.) I failed to anticipate how strongly people would latch onto that exact moment in time as the end of Python 2.
I additionally share the bemusement of some other commentators on this thread to the idea of Python 2 "support", which is not something ever promised to Python 2 (or 3) users by CPython core developers. Essentially, next year, we're changing our "support" policy of Python 2.7 from "none, but we're nice people" to "none".
I understand, but I hope that if a clear bug (perhaps especially a security bug) is found in Python 2.7 (perhaps one that is also in Python 3.x) the core devs will not be in principle opposed to fixing it. At least if one of them (or someone else sufficiently qualified) is prepared to do the work. Especially as you're "essentially" (and you ARE :-) -:) ) "such nice people". Best wishes Rob Cliffe
-- Sumana Harihareswara Changeset Consulting https://changeset.nyc _______________________________________________ Python-Dev mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://firstname.lastname@example.org/message/MXCGMTXD...
Python-Dev mailing list -- email@example.com To unsubscribe send an email to firstname.lastname@example.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://email@example.com/message/ETOBPFVK...
This email has been checked for viruses by AVG. https://www.avg.com