Re: [Twisted-Python] The Python 2.7 Plan

On 17/12/19 3:40 am, Glyph wrote: The whole point would be to define a concrete end in terms of the final release - and I have no doubt that if we say what the date of the final 2.7 release is, Hawkie will get it out /on the dot/, and not a day past its deadline :).  So no way it would be op

Re: [Twisted-Python] The Python 2.7 Plan

On 12/12/19 8:41 am, Wilfredo Sánchez Vega wrote:   I don't object to the final release being in April instead of January, though I'm not sure that the additional release really means we need to do that.  But FWIW I'm in favor of Option 3 / calling 19.4 the final release.  :-)   My sense

Re: [Twisted-Python] The Python 2.7 Plan

> On Dec 16, 2019, at 8:31 AM, Wilfredo Sánchez Vega > wrote: > > On Dec 16, 2019, at 7:10 AM, Glyph > wrote: >> >> When we EOL py27 support for Twisted we should probably do something similar >> so anyone who wants to get a pending fix out as part of the las

Re: [Twisted-Python] The Python 2.7 Plan

On Dec 16, 2019, at 7:10 AM, Glyph wrote: > > When we EOL py27 support for Twisted we should probably do something similar > so anyone who wants to get a pending fix out as part of the last > 27-supporting release has a window to do that. That seems pretty reasonable (as long as it's not ope

Re: [Twisted-Python] The Python 2.7 Plan

> On Dec 11, 2019, at 1:16 PM, Jean-Paul Calderone > wrote: > > On Wed, Dec 11, 2019 at 4:06 PM Wilfredo Sánchez Vega > wrote: > With Python 2.7 support dropping in a matter of weeks, I'd like to pick up > from hawkowl's thread back in March about Python 2.7 s