[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 CPython core developers. Essentially, next year, we're changing our "support" policy of Python 2.7 from "none, but we're nice people" to "none". I understand, but I hope that if a clear bug (perhaps especially a security bug) is found in Python 2.7 (perhaps one that is also in Python 3.x) the core devs will not be in principle opposed to fixing it. At least if one of them (or someone else sufficiently qualified) is prepared to do the work. Especially as you're "essentially" (and you ARE :-) -:) ) "such nice people". Before 2.7.18, sure. After that, in principle and practice, we're opposed. 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. So you may find someone nice enough (or willing enough to accept money (or willing to accept enough money)) to fix an issue, but the fix will have to go somewhere other than the main repo and someone else will have to verify and release it. Cheers, Steve ___ 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/6DINL4MYBCHEVVA6GV44EFJJG2SJ6Y6G/
[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 promised to Python 2 (or 3) > > users by > > CPython core developers. Essentially, next year, we're changing our > > "support" policy of > > Python 2.7 from "none, but we're nice people" to "none". > > I understand, but I hope that if a clear bug (perhaps especially a > > security bug) is found in Python 2.7 (perhaps one that is also in Python > > 3.x) the core devs will not be in principle opposed to fixing it. At > > least if one of them (or someone else sufficiently qualified) is > > prepared to do the work. Especially as you're "essentially" (and you > > ARE :-) -:) ) "such nice people". > > Before 2.7.18, sure. After that, in principle and practice, we're > > opposed. > > 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 be deleted (it's how we handle all EOL versions). -Brett > So you may find someone nice enough (or willing enough to accept money > (or willing to accept enough money)) to fix an issue, but the fix will > have to go somewhere other than the main repo and someone else will have > to verify and release it. > Cheers, > Steve ___ 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/XE3KI5Y7YSUQAUKWJRXHRBXBSUMVDCGR/
[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 be deleted (it's how we handle all EOL versions). 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? -- ~Ethan~ ___ 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/FRDWDPVGEIDSTVJAX2M7Q5RFOQE4KMTH/
[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 refs/tags/3.3` will check out a local `3.3` branch at the tag (resetting the `3.3` local branch if it already existed). The same will work for 2.7 after the branch is deleted. ___ 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/CUMLWTRVXDJJCORQ55JQEQANGNZVWI3P/
[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 our repo. > > > > A final tag of the branch will be made and then the branch will be deleted > > (it's how we handle all EOL versions). > > 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? > If I've understood "tag" correctly, the commits should all remain in the repository for all time, so you should indeed be able to view it as of EOL. You can "git checkout v2.7.18" (or whatever the number is) after cloning the repository. ChrisA ___ 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/7NWOFQBBOSL2GNN6RHVRBUPLUE7ZH3ML/
[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 repo. >> A final tag of the branch will be made and then the branch will be deleted >> (it's how we handle all EOL versions). > > 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? Nothing will be lost, there's no need for a time delay. As we do for every release, there will be a tag created for the final 2.7 release of the form "v2.7.xx". That allows you to checkout the state of any release, including the final 2.7 release. At end-of-life time, we will also create a final "2.7" tag that reflects the final state of the 2.7, in case anything else was checked in following that last release. There will no longer be a "2.7" branch in the repo so it won't be possible to merge 2.7 changes back into the central repo. The 2.7 tag will act as sort of a read-only branch, i.e. you can still do: git checkout 2.7 to access it. If you want, you could create a local branch in your repo. See: https://devguide.python.org/devcycle/#end-of-life-branches -- 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/WVRXP5AVIOUUHQH2ZZ4RLXYRPOJWFFNT/
