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
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
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 re
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
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 pro
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 CPytho
