On 9/17/2019 6:19 PM, Chris Barker via Python-Dev wrote:
On Tue, Sep 17, 2019 at 12:06 PM Peter Wang <pw...@anaconda.com
<mailto:pw...@anaconda.com>> wrote:
On Mon, Sep 16, 2019 at 5:55 PM Chris Barker via Python-Dev
<python-dev@python.org <mailto:python-dev@python.org>> wrote:
Regardless of the date of the final release, no one's Python2
install will stop working, and people will still be able to
download and install that last release.
So I like the metaphor -- it's being "sunset" -- there will be a
long dusk ...... a month or tow makes no difference to anyone's
workflow.
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
communicate a certain... precision and finality to the Dec 31, 2019
date.
That is the nature of countdown clocks ;-).
> I agree with Ned that as a community, we should have a
unified messaging about this.
For that, go to https://python3statement.org/, which more than 120
groups signed so far. I am impressed. That site also (appropriately)
references the PEP. Note that it does NOT have a uniform timeline.
Rather, it is a collective agreement to move on that gives everyone
permission to do so at a somewhat varying (but not indefinitely delayed)
pace.
I already anticipate a final round of
teeth-gnashing as the date draws near, so it would be good to
minimize the room for misunderstandings.
Maybe, maybe not. As you said, 2.7 is not going to be unreleased. At
least some major users that care have or are in the process of moving to
3.x. JPMorgan, for instance, already uses 3.x for new code and expects
to finish moving their 2 million lines within a year.
I think the PEP is clear enough. Anyone who wants anything changed in
2.7 should say so NOW. About a week ago someone asked for a specific
bugfix to be backported and I believe it has or will be done. But this
has become rather rare.
Anything with any significant risk should be in the 2.7.17 October
release. I expect that Benjamin will try to clear any existing backlog
before that release.
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. Coredev release managers are in charge of the
details of making an official PSF release. This does not change with
this one. Benjamin Peterson, at least, will apply patches as he sees
fit until the release. I expect that he will say more about the
shutdown process when he decides.
--
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/UDO4RAY6XOYGKHAHR3XFGTKXYLQSUO65/
