Re: The Python 2.7 Plan
Glyph <[email protected]> Mon, 16 Dec 2019 08:40:42 -0800
| Newsgroups | gmane.comp.python.twisted |
|---|---|
| Message-ID | <[email protected]> |
--===============2170258398934954236== Content-Type: multipart/alternative; boundary="Apple-Mail=_B1B0087F-398C-4C99-A732-6BED6C13AE05" --Apple-Mail=_B1B0087F-398C-4C99-A732-6BED6C13AE05 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Dec 16, 2019, at 8:31 AM, Wilfredo S=C3=A1nchez Vega = <[email protected]> wrote: >=20 > On Dec 16, 2019, at 7:10 AM, Glyph <[email protected] = <mailto:[email protected]>> wrote: >>=20 >> 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. >=20 > That seems pretty reasonable (as long as it's not open-ended). 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 open-ended=10. -g --Apple-Mail=_B1B0087F-398C-4C99-A732-6BED6C13AE05 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br = class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div = class=3D"">On Dec 16, 2019, at 8:31 AM, Wilfredo S=C3=A1nchez Vega = <<a href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>> wrote:</div><br = class=3D"Apple-interchange-newline"><div class=3D""><meta = http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii" = class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: = space; line-break: after-white-space;" class=3D"">On Dec 16, 2019, at = 7:10 AM, Glyph <<a href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>> wrote:<br class=3D""><div = class=3D""><blockquote type=3D"cite" class=3D""><br = class=3D"Apple-interchange-newline"><div class=3D""><div = style=3D"caret-color: rgb(0, 0, 0); font-family: SFHello-Regular; = font-size: 14px; font-style: normal; font-variant-caps: normal; = font-weight: normal; letter-spacing: normal; text-align: start; = text-indent: 0px; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: = none;" class=3D"">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.</div></div></blockquote></div><br class=3D""><div class=3D""> = That seems pretty reasonable (as long as it's not = open-ended).</div></div></div></blockquote><br class=3D""></div><div>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 <i class=3D"">on the dot</i><span = style=3D"font-style: normal;" class=3D"">, and not a day past its = deadline :). So no way it would be = open-ended=10.</span></div><div><span style=3D"font-style: normal;" = class=3D""><br class=3D""></span></div><div><span style=3D"font-style: = normal;" class=3D"">-g</span></div><br class=3D""></body></html>= --Apple-Mail=_B1B0087F-398C-4C99-A732-6BED6C13AE05-- --===============2170258398934954236== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVHdpc3RlZC1Q eXRob24gbWFpbGluZyBsaXN0ClR3aXN0ZWQtUHl0aG9uQHR3aXN0ZWRtYXRyaXguY29tCmh0dHBz Oi8vdHdpc3RlZG1hdHJpeC5jb20vY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3R3aXN0ZWQtcHl0 aG9uCg== --===============2170258398934954236==--