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

Oh, that makes your original email make much more sense (at least to me). I also interpreted it to mean you were interested in extending the EOL date out further, rather than pointing out that it should probably already have been switched from “bugfix” to “security” status. —Chris On Wed, Mar

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

On 3/14/2018 9:16 AM, Michael Scott Cuthbert wrote: I’m guessing my first message was unclear or able to be misunderstood in some part — I’m one of the frequent contributors to python3statement.org and have moved my own Python projects to Py3 only (the main one,

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

Speaking from the sidelines, I'd say that any further backporting of non-security fixes would appear to be throwing good development effort away, This software is less than two years from the extremely well-heralded end of its life and people are expecting enhancements? It's a cold, ungrateful

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

> 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/. I’m guessing my first message was unclear or able to be misunderstood in some part —

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

On 2018-03-12, 13:13 GMT, Nick Coghlan wrote: > +1 from me, as even if commercial redistributors do decide > they want to collaborate on a post-2020 Python 2.7 maintenance > branch, there's no technical reason that that needs to live > under the "python" GitHub organisation, and some solid >

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

On 11 March 2018 at 11:54, 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,

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

Sounds good to me. I've updated the PEP to say 2.7 is completely dead on Jan 1 2020. The final release may not literally be on January 1st, but we certainly don't want to support 2.7 through all of 2020. On Sat, Mar 10, 2018, at 18:54, Guido van Rossum wrote: > Let's not play games with

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

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

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

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

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

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

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

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