On Tue, Sep 17, 2019 at 10:39 PM Terry Reedy <tjre...@udel.edu> 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 <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&R            (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/

Reply via email to