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

Benjamin or others: could you please review https://github.com/python/cpython/pull/19229 to "Add an optional obsolete header." to the 2.7 documentation today or tomorrow? Much thanks. ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe

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

Thanks. I'm working to get https://github.com/python/steering-council/issues/3 resolved by April 17th to add an informational header to all the deep links within https://docs.python.org/2/* . I welcome help on the pull requests linked from that issue (such as

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

On Fri, Mar 27, 2020, at 11:49, Sumana Harihareswara wrote: > Benjamin: now that PyCon 2020 has been cancelled, are you considering > releasing 2.7.18 slightly earlier? The plan is to follow the dates in PEP 373. ___ Python-Dev mailing list --

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

I'm sorry, I should have been more specific. I'm talking about the "switch to Python 3" banner that we need to add per discussion in https://github.com/python/steering-council/issues/3 . I am pretty sure it's not too late for that. -Sumana On 3/29/20 10:23 AM, Victor Stinner wrote: IMHO it's

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

IMHO it's too late to touch the Python 2.7 documentation. Victor Le dim. 29 mars 2020 à 16:01, Sumana Harihareswara a écrit : > > On 3/27/20 12:49 PM, Sumana Harihareswara wrote: > > Benjamin: now that PyCon 2020 has been cancelled, are you considering > > releasing 2.7.18 slightly earlier? >

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

On 3/27/20 12:49 PM, Sumana Harihareswara wrote: Benjamin: now that PyCon 2020 has been cancelled, are you considering releasing 2.7.18 slightly earlier? (I ask because: before you do that, I would like to submit some changes to the documentation for the 2.7 branch, to indicate to users that

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

Benjamin: now that PyCon 2020 has been cancelled, are you considering releasing 2.7.18 slightly earlier? -- Sumana Harihareswara Changeset Consulting https://changeset.nyc ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an

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

Per https://discuss.python.org/t/petition-abandon-plans-to-ship-a-2-7-18-in-april/2946/ I have now: * written a PR to update PEP 373 to mark that the code freeze happened on 1 January https://github.com/python/peps/pull/1304 * updated the Python 3 Q

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

On Sep 26, 2019, at 14:50, Ethan Furman wrote: > > On 09/26/2019 09:28 AM, Brett Cannon wrote: >> Steve Dower wrote: > >>> The biggest thing that will change is that all our CI systems will stop >>> testing 2.7, and there's a good chance we'll lock (or delete?) the 2.7 >>> branch from our

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

On Fri, Sep 27, 2019 at 5:04 AM Ethan Furman wrote: > > On 09/26/2019 09:28 AM, Brett Cannon wrote: > > Steve Dower wrote: > > >> The biggest thing that will change is that all our CI systems will stop > >> testing 2.7, and there's a good chance we'll lock (or delete?) the 2.7 > >> branch from

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

On Thu, Sep 26, 2019 at 1:58 PM Ethan Furman wrote: > Will there be a time delay between the final tagging and the deletion so any > who would like the repo in its final state can clone it at that point? No need; you can try this with any currently closed branch like 3.3: `git checkout -B 3.3

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

On 09/26/2019 09:28 AM, Brett Cannon wrote: Steve Dower wrote: The biggest thing that will change is that all our CI systems will stop testing 2.7, and there's a good chance we'll lock (or delete?) the 2.7 branch from our repo. A final tag of the branch will be made and then the branch will

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

Steve Dower wrote: > On 25Sep2019 2140, Benjamin Peterson wrote: > > On Wed, Sep 25, 2019, at 17:25, Rob Cliffe via > > Python-Dev wrote: > > I > > additionally share the bemusement of some other commentators on this thread > > to the idea of > > Python 2 "support", which is not something ever

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

On 25Sep2019 2140, Benjamin Peterson wrote: On Wed, Sep 25, 2019, at 17:25, Rob Cliffe via Python-Dev wrote: I additionally share the bemusement of some other commentators on this thread to the idea of Python 2 "support", which is not something ever promised to Python 2 (or 3) users by

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

On Wed, Sep 25, 2019, at 17:25, Rob Cliffe via Python-Dev wrote: > > I additionally share the bemusement of some other commentators on this > > thread to the idea of Python 2 "support", which is not something ever > > promised to Python 2 (or 3) users by CPython core developers. Essentially,

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

On 24/09/2019 04:21:45, Benjamin Peterson wrote: On Fri, Sep 13, 2019, at 18:18, Sumana Harihareswara wrote: Hi. I've joined python-dev to participate in this thread (I don't have email delivery turned on; I'll be checking back via the web). sorry :) Benjamin, I am sorry that I didn't

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

On Wed, Sep 18, 2019, at 19:23, Kyle Stanley wrote: > Benjamin, what are you thoughts on usage of the "needs backport to 2.7" > label? For most of the PRs I've reviewed I tend to avoid adding it > myself, but I've seen it used periodically. It seems to be used rather > infrequently >

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

On Fri, Sep 13, 2019, at 18:18, Sumana Harihareswara wrote: > Hi. I've joined python-dev to participate in this thread (I don't have > email delivery turned on; I'll be checking back via the web). sorry :) > > Benjamin, I am sorry that I didn't check in with you, and assumed that > January

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

Stefan Behnel wrote: > Ned Batchelder schrieb am 10.09.19 um 16:54: > > this seems confusing to me > > What does the "official EOL date" mean if there's a release in April? It means we should all consider Python 2.7 EOL'ed come January 1 and Benjamin will make a release when it's convenient, and

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

Chris Barker wrote: > On Tue, Sep 17, 2019 at 10:39 PM Terry Reedy tjre...@udel.edu wrote: > > 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

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

Kyle Stanley wrote: > Benjamin, what are you thoughts on usage of the "needs backport to 2.7" > label? For most of the PRs I've reviewed I tend to avoid adding it myself, > but I've seen it used periodically. It seems to be used rather infrequently > ( >

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

On Wed, 18 Sep 2019 at 18:52, Chris Barker via Python-Dev wrote: > it would be good to be clear what EXACTLY "support stops" means. Generally, when people ask questions like this, I struggle, because it's not altogether clear to me what they think they mean in the first place by the "support"

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

Benjamin, what are you thoughts on usage of the "needs backport to 2.7" label? For most of the PRs I've reviewed I tend to avoid adding it myself, but I've seen it used periodically. It seems to be used rather infrequently (

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

On 9/18/2019 1:45 PM, Chris Barker via Python-Dev wrote: I'm just echoing (and agreeing with) Peter here -- there is a specific date in the PEP (January 1 2020), and that has been adopted by pythonclock and others, so it would be good to be clear what EXACTLY "support stops" means. In terms

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

On Tue, Sep 17, 2019 at 10:39 PM Terry Reedy wrote: > 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

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

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

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

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

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

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

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

Hi. I've joined python-dev to participate in this thread (I don't have email delivery turned on; I'll be checking back via the web). Benjamin, I am sorry that I didn't check in with you, and assumed that January 1, 2020 would be the the date of the final 2.7 point release. (My understanding

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

I think Ned's concerns are real, and the sunset-python-2 page could use some wordsmithing to explain that even though support ends on Jan 1, there will be a wrap-up release some time after that, but it won't incorporate any changes made or proposed after Jan 1. Another place where that

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

I think it’s fine to say that Python 2 EOL is on January 1, 2020. That doesn’t preclude a Contractual Obligation release in April. There’s precedence in the last Python 1 (1.6.1) release! https://en.wikipedia.org/wiki/Monty_Python%27s_Contractual_Obligation_Album -Barry > On Sep 10, 2019,

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

*RE: Ned's comments -- *That is the same reaction I had when I read through this thread. *RE: Tal's comment - *I could see this making sense as an explanation. *RE: Guido's comment* This makes me think that April 2020 is not a thing. And if Ben is supporting solo, then can people email him

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

On Tue, Sep 10, 2019 at 10:03 PM Ned Batchelder wrote: > > I'm not looking forward to answering questions from the public about why > the PSF is writing dire and specific warnings like "We have decided that > January 1, 2020, will be the day that we sunset Python 2," while the > core devs are

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

On Wed, Sep 11, 2019 at 5:05 AM Ned Batchelder wrote: > > On 9/10/19 11:06 AM, Benjamin Peterson wrote: > > On Tue, Sep 10, 2019, at 15:54, Ned Batchelder wrote: > >> Maybe I'm not involved enough in the release process, but this seems > >> confusing to me. On the same day that the PSF put up a

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

On 9/10/19 11:06 AM, Benjamin Peterson wrote: On Tue, Sep 10, 2019, at 15:54, Ned Batchelder wrote: Maybe I'm not involved enough in the release process, but this seems confusing to me.  On the same day that the PSF put up a page about the 1/1/2020 date, we choose April 2020 as the last

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

Ned Batchelder schrieb am 10.09.19 um 16:54: > this seems confusing to me > What does the "official EOL date" mean if there's a release in April? Also, what day in April? For example, planning the release for the 1st could possibly add further to the confusion. Stefan

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

On 9/10/2019 10:54 AM, Ned Batchelder wrote: What does the "official EOL date" mean if there's a release in April? To me, it means that coredevs freely patching 2.7 ends 1/1/2020 and that the final release will occur by PyCon and that everything between the two is at the discretion of

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

It probably means that from January to April Benjamin will be too busy porting Dropbox to Python 3 to have time for Python 2 support. Or possibly it means that until PyCon 2020, there will be only one core developer supporting Python 2, and it will be Benjamin. You choose. :-) On Tue, Sep 10,

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

On Tue, Sep 10, 2019, at 15:54, Ned Batchelder wrote: > Maybe I'm not involved enough in the release process, but this seems > confusing to me.  On the same day that the PSF put up a page about the > 1/1/2020 date, we choose April 2020 as the last release?  Why?  I > thought the point was to

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

Maybe I'm not involved enough in the release process, but this seems confusing to me.  On the same day that the PSF put up a page about the 1/1/2020 date, we choose April 2020 as the last release?  Why?  I thought the point was to save core devs efforts.  Is this an unofficial grace period? 

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

It's not dead, it's just restin' after a particularly heavy release process. regards Steve Holden On Mon, Sep 9, 2019 at 4:24 PM Rhodri James wrote: > On 09/09/2019 15:51, brian.sk...@gmail.com wrote: > > it's getting better? > > No it's not, it'll be stone dead in a moment. > > -- >

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

On 09/09/2019 15:51, brian.sk...@gmail.com wrote: it's getting better? No it's not, it'll be stone dead in a moment. -- Rhodri James *-* Kynesim Ltd ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to

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

it's getting better? ___ 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

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

It says it's feeling fine ;-) Regards Antoine. On Mon, 09 Sep 2019 14:29:51 +0100 "Benjamin Peterson" wrote: > Hi all, > It's finally time to schedule the last releases in Python 2's life. There > will be two more releases of Python 2.7: Python 2.7.17 and Python 2.7.18. > > Python 2.7.17