[Python-Dev] Re: The Python 2 death march

[Kyle Stanley]

Benjamin, what are you thoughts on usage of the "needs backport to 2.7"
label? For most of the PRs I've reviewed I tend to avoid adding it myself,
but I've seen it used periodically. It seems to be used rather infrequently
(
https://github.com/python/cpython/pulls?q=is%3Apr+label%3A%22needs+backport+to+2.7%22+is%3Amerged),
but I'm not entirely clear on when it should be used, particularly for
documentation-related PRs.

Also, is there an official date when the label will be removed? Removing
the backport label seems to generally be at the discretion of the release
manager for that version, but I was curious as to whether it would be
removed on the sunset date or prior to then. Without the label, backport
PRs can still be opened manually of course, but removing it would probably
help to discourage 2.7 backports.

On Mon, Sep 9, 2019 at 9:38 AM Benjamin Peterson 
wrote:

> Hi all,
> It's finally time to schedule the last releases in Python 2's life. There
> will be two more releases of Python 2.7: Python 2.7.17 and Python 2.7.18.
>
> Python 2.7.17 release candidate 1 will happen on October 5th followed by
> the final release on October 19th.
>
> I'm going to time Python 2.7.18 to coincide with PyCon 2020 in April, so
> attendees can enjoy some collective catharsis. We'll still say January 1st
> is the official EOL date.
>
> Thanks to Sumana Harihareswara, there's now a FAQ about the Python 2
> sunset on the website: https://www.python.org/doc/sunset-python-2/
>
> Regards,
> Benjamin
> ___
> Python-Dev mailing list -- python-dev@python.org
> To unsubscribe send an email to python-dev-le...@python.org
> https://mail.python.org/mailman3/lists/python-dev.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-dev@python.org/message/APWHFYQDKNVYQAK3HZMBGQIZHAVRHCV2/
>
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/NYIVL47NMGMSWTF5FQCZQF2ZWPA6I2SH/

[Python-Dev] Re: The Python 2 death march

[Terry Reedy]

On 9/18/2019 1:45 PM, Chris Barker via Python-Dev wrote:

I'm just echoing (and agreeing with) Peter here -- there is a specific 
date in the PEP (January 1 2020), and that has been adopted by 
pythonclock and others, so it would be good to be clear what EXACTLY 
"support stops" means.


In terms of implementation, I don't think all details are decided yet, 
so that 'EXACTLY' does not yet exist, and may not until after the fact. 
But I already said what it means for users. If you want a change, ask 
for it now.  Even late December may be too late.


For coredevs, I believe it means that routine patching stops and we 
should act as if the 2.7 branch were in the release candidate stage, 
where patches go through the release manager.


To put is another way, support is already tapering off.  And most of us 
who have not already washed out hands of 2.7 will on Jan 1.


And I misspoke, it would be "date on when the last patch would 
potentially be considered" And if that's not the case, then why have a 
date other than the date of the last release ??


I think you are missing the distinction between routine patches, which 
any committer can make, and which should stop about Jan 1, and release 
candidate patches, more or less restricted to the release manager.  I 
expect his last patch will be just before release, follows by closing 
2.7 just after.  But I don't care about the details and neither should 
most anyone else.



--
Terry Jan Reedy
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/TRKGOHUNNMLPIOFGB3BHTXPNLS6LBKIB/

[Python-Dev] Re: The Python 2 death march

[Chris Barker via Python-Dev]

On Tue, Sep 17, 2019 at 10:39 PM Terry Reedy  wrote:

> I agree.  The thread title is a bit extreme.  There will be a long
> twilight.
>
> > Metaphorically that is correct, but at the same time there are
> > things like https://pythonclock.org  which
>
> is one person's very unofficial site.  It interprets and references
> https://www.python.org/dev/peps/pep-0373/#maintenance-releases


I can't see a way to contact the owner of that site (is it Guido??), but if
you are reading this list, maybe a sunset metaphor would be nice.

I like that: when you are watching a sunset, you can look out at the
horizon, hoping to see the green flash, and there is a clear moment when
the sun fully drops below the horizon -- but it doesn't suddenly get dark
:-)

> Yes, it would, but if we are emphasizing that hard date,
>
> But we core developers are not, other than what the PEP says:
> "Support officially stops January 1 2020, but the final release will
> occur after that date.  Actually, support has already been tapering off
> for over 3 or 4 years and 2.7 patches are now a slow dribble.  What is
> ending is free build and security from us.
>
> > we need to  emphasise that it is a hard date on when the last patch
> > would  potentially be applied,
>
> Not really your concern.


I'm just echoing (and agreeing with) Peter here -- there is a specific date
in the PEP (January 1 2020), and that has been adopted by pythonclock and
others, so it would be good to be clear what EXACTLY "support stops" means.

And I misspoke, it would be "date on when the last patch would potentially
be considered" And if that's not the case, then why have a date other than
the date of the last release ??

Personally, I have no angst over a few months here or there, but apparently
some people do.

-CHB


-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR(206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115   (206) 526-6317   main reception

chris.bar...@noaa.gov
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/EMDC6YMASGWTXJJZC6VLNCGKM6FONYHG/