[Python-Dev] Re: Python library maintainers: PEP 602 needs your feedback

[Brett Cannon]

At the Python core dev sprints we created a new "PEPs" category for PEP 
discussions to go and that's open to the public.
___
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/KUAJAFQL45OHWEISNYBL42UNKFMNB5MU/

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

[Chris Barker via Python-Dev]

Peter, I think that went just to me, which I suspect was not what you
intended, so I've brought it back on the list:

On Tue, Sep 17, 2019 at 12:06 PM Peter Wang  wrote:

> On Mon, Sep 16, 2019 at 5:55 PM Chris Barker via Python-Dev <
> 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.
>>
>
> Metaphorically that is correct, but at the same time there are things like
> https://pythonclock.org which communicate a certain... precision and
> finality to the Dec 31, 2019 date.  I agree with Ned that as a community,
> we should have a unified messaging about this.  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.
>

Yes, it would, but if we are emphasizing that hard date, we need to
emphasise that it is a hard date on when the last patch would potentially
be applied, and other than that, there is no discontinuity ...

-CHB



>
> Cheers,
> Peter
>


-- 

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/PLQ2SUAUJ5MPEAWY54Z5A6BVH5F7GRTB/

[Python-Dev] 3.7.5rc1 release blocked (Re: 3.7.5rc1 cutoff ahead)

[Ned Deily]

2019-09-17 Update: as of the scheduled cutoff time earlier today, we had two 
recently identified release blocker issues open.  Thanks to Andrew and Yury, 
one of them is now resolved with code (bpo-38013).  The other (bpo-30458 and 
bpo-36274) remains unresolved at this point.  Because the issue(s) involve an 
apparent regression introduced in a fix for a security issue in 3.7.4, a 
regression that has affected at least one third-party project (and has the 
potential to affect releases from other branches), I think we should resolve 
this now.  A number of core devs have been involved in these two issues most 
recently Jason.  I'm am going to delay tagging the release for at least a day.  
Anything you can do to help resolve this one, especially if you have already 
been involved with it, would be greatly appreciated.

https://bugs.python.org/issue30458
  [security][CVE-2019-9740][CVE-2019-9947] HTTP Header Injection (follow-up of 
CVE-2016-5699)

https://bugs.python.org/issue36274
  http.client cannot send non-ASCII request lines


On Sep 9, 2019, at 07:10, Ned Deily  wrote:
> https://discuss.python.org/t/3-7-5rc1-cutoff-ahead/2288
> 
> A reminder: it is time for the next quarterly maintenance release of Python 
> 3.7. The cutoff for **3.7.5rc1** is scheduled for this coming Monday 
> (2019-09-16) by the end of day AOE. Please review open issues and ensure that 
> any that you believe need to be addressed in 3.7.5 are either resolved or 
> marked as a **release blocker**.  Any assistance you can provide in helping 
> resolve issues will be greatly appreciated.  Following the rc1 cutoff, 
> changes merged to the 3.7 branch will be released in 3.7.6 three months from 
> now unless you mark the issue as a release blocker prior to **3.7.5 final**, 
> planned for release on **2019-09-30** and explain why the change should be 
> cherry-picked into the final release.
> 
> Thanks to everyone who has been helping to ensure the continued success of 
> Python 3.7! Our users truly appreciate it and are showing their confidence in 
> us by the rapid adoption of these latest releases.
> 
> P.S. A number of core developers are participating in this year's core 
> developer sprint taking place this week in London.  So it is a good time to 
> catch many of us in the same place at the same time (and British Summer Time, 
> at that).
> 
> https://www.python.org/dev/peps/pep-0537/

--
  Ned Deily
  n...@python.org -- []
___
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/V3R3HSUIU3ZOXM776BSS4OKEU3G2RJMG/

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

[Terry Reedy]

On 9/17/2019 6:19 PM, Chris Barker via Python-Dev wrote:

On Tue, Sep 17, 2019 at 12:06 PM Peter Wang > wrote:


On Mon, Sep 16, 2019 at 5:55 PM Chris Barker via Python-Dev
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  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/