[Python-Dev] Python 2.7 -- bugfix or security before EOL?

2018-03-10 Thread Michael Scott Cuthbert 
I notice on https://devguide.python.org that Python 3.5 is in “security” status 
with an EOL of 2020-09-13 but Python 2.7 is in “bugfix” and has a likely 
earlier EOL.  Will there be a period where Py2.7 is in security-only status 
before hitting EOL?  Even if the EOL is set at the last possible date of 
2020-12-31, it still is in the time period before EOL that other recent 
versions have gone to security only.

(obviously recognizing that Py2.7 EOL is not just another EOL)

I tried searching in archives for anything related to this status, but couldn’t 
find anything.  apologies if I missed a discussion.

- Michael Cuthbert

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python 2.7 -- bugfix or security before EOL?

2018-03-10 Thread Terry Reedy 

On 3/10/2018 4:59 PM, Michael Scott Cuthbert wrote:
I notice on https://devguide.python.org that Python 3.5 is in “security” 
status with an EOL of 2020-09-13 but Python 2.7 is in “bugfix” and has a 
likely earlier EOL.


There is no relation between the two, or between 2.7 and any other 
version.  2.7 is a completely special case.



 Will there be a period where Py2.7 is in security-only status before hitting 
EOL?


https://www.python.org/dev/peps/pep-0373 gives the public status.  When 
Benjamin Peterson want to add something, he will.


Already, the main emphasis is on security, build, and test 
infrastructure fixes.  Backporting bug and doc fixes is at developer 
discretion.



 Even if the EOL is set at the last possible date of 2020-12-31,


Benjamin Peterson will decide when he decides.  He has not yet announced 
a date for a 2018 release.


People have mostly proposed either Jan 1 or sometime late spring related 
to PyCon.  If you want something definite for your own planning, I 
recommend that you assume Jan 1.


it still is in the time period before 
EOL that other recent versions have gone to security only.


Again, not relevant.

You might want to read http://python3statement.org/.

Some major projects (like Django, I believe) have already put their last 
2.x compatible version into bug-fix only mode and expect to stop 
patching it before 2020.


--
Terry Jan Reedy


___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python 2.7 -- bugfix or security before EOL?

2018-03-10 Thread Guido van Rossum 
Let's not play games with semantics. The way I see the situation for 2.7 is
that EOL is January 1st, 2020, and there will be no updates, not even
source-only security patches, after that date. Support (from the core devs,
the PSF, and python.org) stops completely on that date. If you want support
for 2.7 beyond that day you will have to pay a commercial vendor. Of course
it's open source so people are also welcome to fork it. But the core devs
have toiled long enough, and the 2020 EOL date (an extension from the
originally annouced 2015 EOL!) was announced with sufficient lead time and
fanfare that I don't feel bad about stopping to support it at all.

On Sat, Mar 10, 2018 at 5:36 PM, Terry Reedy  wrote:

> On 3/10/2018 4:59 PM, Michael Scott Cuthbert wrote:
>
>> I notice on https://devguide.python.org that Python 3.5 is in “security”
>> status with an EOL of 2020-09-13 but Python 2.7 is in “bugfix” and has a
>> likely earlier EOL.
>>
>
> There is no relation between the two, or between 2.7 and any other
> version.  2.7 is a completely special case.
>
>  Will there be a period where Py2.7 is in security-only status before
>> hitting EOL?
>>
>
> https://www.python.org/dev/peps/pep-0373 gives the public status.  When
> Benjamin Peterson want to add something, he will.
>
> Already, the main emphasis is on security, build, and test infrastructure
> fixes.  Backporting bug and doc fixes is at developer discretion.
>
>  Even if the EOL is set at the last possible date of 2020-12-31,
>>
>
> Benjamin Peterson will decide when he decides.  He has not yet announced a
> date for a 2018 release.
>
> People have mostly proposed either Jan 1 or sometime late spring related
> to PyCon.  If you want something definite for your own planning, I
> recommend that you assume Jan 1.
>
> it still is in the time period before EOL that other recent versions have
>> gone to security only.
>>
>
> Again, not relevant.
>
> You might want to read http://python3statement.org/.
>
> Some major projects (like Django, I believe) have already put their last
> 2.x compatible version into bug-fix only mode and expect to stop patching
> it before 2020.
>
> --
> Terry Jan Reedy
>
>
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%
> 40python.org
>



-- 
--Guido van Rossum (python.org/~guido)
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Git hub : CLA Not Signed label

2018-03-10 Thread Anthony Flury via Python-Dev 

All,
I submitted two Pull Requests last Sunday, only a few hours after I 
signed the CLA.


I understand why the 'Knights who say ni' marked the Pull request as 
'CLA Not Signed' Label at the time I submitted the Pull requests, but I 
was wondering when the Labels get reset.


How often (if at all) does the bot look at old pull requests ?

Thanks for any help you can give, I am sorry if the question sounds basic.
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Git hub : CLA Not Signed label

2018-03-10 Thread Ned Deily 
On Mar 10, 2018, at 21:58, Anthony Flury via Python-Dev  
wrote:
> I submitted two Pull Requests last Sunday, only a few hours after I signed 
> the CLA.
> 
> I understand why the 'Knights who say ni' marked the Pull request as 'CLA Not 
> Signed' Label at the time I submitted the Pull requests, but I was wondering 
> when the Labels get reset.

I've reset both manually.  Thanks for the heads up.  Now to get reviews!


--
  Ned Deily
  [email protected] -- []

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python 2.7 -- bugfix or security before EOL?

2018-03-10 Thread Terry Reedy 

On 3/10/2018 8:54 PM, Guido van Rossum wrote:
Let's not play games with semantics. The way I see the situation for 2.7 
is that EOL is January 1st, 2020, and there will be no updates, not even 
source-only security patches, after that date. Support (from the core 
devs, the PSF, and python.org ) stops completely on 
that date.


+1 from me.  If so, then that should be added to the PEP and announced 
at PyCon, to end major questions* and speculation.


* There are still minor details of when patches are cutoff (is that EOL, 
on Jan 1?) and when the rc and final releases appear (whenever ready 
after cutoff?)


--
Terry Jan Reedy

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Git hub : CLA Not Signed label

2018-03-10 Thread Terry Reedy 

On 3/10/2018 9:58 PM, Anthony Flury via Python-Dev wrote:

All,
I submitted two Pull Requests last Sunday, only a few hours after I 
signed the CLA.


When processed properly, a day to a week, usually, a * will appear after 
your name on any tracker (bpo) post.


I understand why the 'Knights who say ni' marked the Pull request as 
'CLA Not Signed' Label at the time I submitted the Pull requests, but I 
was wondering when the Labels get reset.


When a core developer manually removes the label, as Ned did, and the 
bot checks with the tracker and agrees.



How often (if at all) does the bot look at old pull requests ?


Never, that I know of.


Thanks for any help you can give, I am sorry if the question sounds basic.


One can also request help on core-mentorship list.  A link to the PR helps.

--
Terry Jan Reedy

___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com