Re: 2.7 EOL = 2020 January 1
On 13/03/18 18:30, Tim Chase wrote: On 2018-03-13 10:58, Terry Reedy wrote: Two days later, Benjamin Peterson, the 2.7 release manager, replied "Sounds good to me. I've updated the PEP to say 2.7 is completely dead on Jan 1 2020." adding "The final release may not literally be on January 1st". Am I the only one saddened by this announcement? I mean, it could have been something like """ "VOOM"?!? Mate, 2.7 wouldn't "voom" if you put four million volts through it! It's bleedin' demised! It's not pinin'! It's passed on! This 2.x series is no more! It has ceased to be! It's expired and gone to meet its maker! It's a stiff! Bereft of life, it rests in peace! If you hadn't nailed it to your dependencies it'd be pushing up the daisies! Its metabolic processes are now 'istory! It's off the twig! It's kicked the bucket, it's shuffled off its mortal coil, run down the curtain and joined the bleedin' choir invisible!! THIS IS AN EX-VERSION!! """ Pythonically-yers, -tkc I'd still like to know what the core developers have ever done for us. Apart from . -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence -- https://mail.python.org/mailman/listinfo/python-list
Re: 2.7 EOL = 2020 January 1
On Tue, 13 Mar 2018 10:58:42 -0400, Terry Reedy wrote: > On March 10, on thread "Python 2.7 -- bugfix or security before EOL?", > Guido van Russum wrote > > "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. [...]" *dances a happy dance* Thanks Terry for posting the message, thanks Guido for drawing a line in the sand and sticking with it, and thanks to all the core devs who have worked so hard to keep the transition from 2 -> 3 as gentle as possible. Like Python 1 before it, Python 2 has been a wonderful language to work with, but it is long past time to move on to Python 3. Or pay for the support. We can only ask volunteers for so much. -- Steve -- https://mail.python.org/mailman/listinfo/python-list
Re: 2.7 EOL = 2020 January 1
On Wed, Mar 14, 2018 at 5:30 AM, Tim Chase wrote: > On 2018-03-13 10:58, Terry Reedy wrote: >> Two days later, Benjamin Peterson, the 2.7 release manager, replied >> "Sounds good to me. I've updated the PEP to say 2.7 is completely >> dead on Jan 1 2020." adding "The final release may not literally be >> on January 1st". > > Am I the only one saddened by this announcement? I mean, it could > have been something like > > """ > "VOOM"?!? Mate, 2.7 wouldn't "voom" if you put four million volts > through it! It's bleedin' demised! It's not pinin'! It's passed on! > This 2.x series is no more! It has ceased to be! It's expired and > gone to meet its maker! It's a stiff! Bereft of life, it rests in > peace! If you hadn't nailed it to your dependencies it'd be pushing > up the daisies! Its metabolic processes are now 'istory! It's off > the twig! It's kicked the bucket, it's shuffled off its mortal coil, > run down the curtain and joined the bleedin' choir invisible!! > THIS IS AN EX-VERSION!! > """ > Wait until Jan 2nd 2020. Then post that. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: 2.7 EOL = 2020 January 1
On 2018-03-13 10:58, Terry Reedy wrote: > Two days later, Benjamin Peterson, the 2.7 release manager, replied > "Sounds good to me. I've updated the PEP to say 2.7 is completely > dead on Jan 1 2020." adding "The final release may not literally be > on January 1st". Am I the only one saddened by this announcement? I mean, it could have been something like """ "VOOM"?!? Mate, 2.7 wouldn't "voom" if you put four million volts through it! It's bleedin' demised! It's not pinin'! It's passed on! This 2.x series is no more! It has ceased to be! It's expired and gone to meet its maker! It's a stiff! Bereft of life, it rests in peace! If you hadn't nailed it to your dependencies it'd be pushing up the daisies! Its metabolic processes are now 'istory! It's off the twig! It's kicked the bucket, it's shuffled off its mortal coil, run down the curtain and joined the bleedin' choir invisible!! THIS IS AN EX-VERSION!! """ Pythonically-yers, -tkc -- https://mail.python.org/mailman/listinfo/python-list
2.7 EOL = 2020 January 1
On March 10, on thread "Python 2.7 -- bugfix or security before EOL?", Guido van Russum wrote "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." Two days later, Benjamin Peterson, the 2.7 release manager, replied "Sounds good to me. I've updated the PEP to say 2.7 is completely dead on Jan 1 2020." adding "The final release may not literally be on January 1st". https://www.python.org/dev/peps/pep-0373/ now says "2.7 will receive bugfix support until January 1, 2020." -- Terry Jan Reedy -- https://mail.python.org/mailman/listinfo/python-list
