Re: The Python 2.7 Plan
Wilfredo Sánchez Vega <[email protected]> Wed, 11 Dec 2019 13:41:50 -0800
| Newsgroups | gmane.comp.python.twisted |
|---|---|
| Message-ID | <[email protected]> |
--===============4131752959112036442== Content-Type: multipart/alternative; boundary="Apple-Mail=_D5BE4171-1740-4024-9727-D5A98C74C67D" --Apple-Mail=_D5BE4171-1740-4024-9727-D5A98C74C67D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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 is that there was consensus on hawkowl's proposal except for, = I think: 1- Should we drop the idea of a 2.7 maintenance branch? 2- It seems we need to fix the bug in twisted.names first. 3- Choosing a final 2.7 release date. -wsv > On Dec 11, 2019, at 1:16 PM, Jean-Paul Calderone = <[email protected]> wrote: >=20 > On Wed, Dec 11, 2019 at 4:06 PM Wilfredo S=C3=A1nchez Vega = <[email protected] <mailto:[email protected]>> 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 support for = Twisted. >=20 > Despite the widely circulated January 1 2020 date, it seems that = python-dev nevertheless plans to make a Python 2.7 release in April 2020 = - https://www.python.org/dev/peps/pep-0373/ = <https://www.python.org/dev/peps/pep-0373/> >=20 > This is not to say the questions here don't need answering or that = there isn't some urgency at this point, but it seems like the January 1 = date is essentially an arbitrary deadline without a clear connection to = the support status of CPython 2.7. >=20 > Or does anyone know a different way to reconcile these apparently = conflicting dates? >=20 > Jean-Paul --Apple-Mail=_D5BE4171-1740-4024-9727-D5A98C74C67D 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""><div = class=3D""> 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. :-)</div><div class=3D""><br = class=3D""></div><div class=3D""> My sense is that there was = consensus on hawkowl's proposal except for, I think:</div><div = class=3D""><br class=3D""></div><div class=3D""><span = class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>1- Should = we drop the idea of a 2.7 maintenance branch?</div><div class=3D""><span = class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>2- It = seems we need to fix the bug in twisted.names first.</div><div = class=3D""><span class=3D"Apple-tab-span" style=3D"white-space:pre"> = </span>3- Choosing a final 2.7 release date.</div><div class=3D""><br = class=3D""></div><div class=3D""><span class=3D"Apple-tab-span" = style=3D"white-space:pre"> </span>-wsv</div><br class=3D""><div><br = class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Dec = 11, 2019, at 1:16 PM, Jean-Paul Calderone <<a = href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>> wrote:</div><br = class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" = class=3D""><div dir=3D"ltr" class=3D"">On Wed, Dec 11, 2019 at 4:06 PM = Wilfredo S=C3=A1nchez Vega <<a href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>> wrote:<br class=3D""></div><div = class=3D"gmail_quote"><blockquote class=3D"gmail_quote" = style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid = rgb(204,204,204);padding-left:1ex"> 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 support for Twisted.<br = class=3D""></blockquote><div class=3D""><br class=3D""></div><div = class=3D"">Despite the widely circulated January 1 2020 date, it seems = that python-dev nevertheless plans to make a Python 2.7 release in April = 2020 - <a href=3D"https://www.python.org/dev/peps/pep-0373/" = class=3D"">https://www.python.org/dev/peps/pep-0373/</a></div><div = class=3D""><br class=3D""></div><div class=3D"">This is not to say the = questions here don't need answering or that there isn't some urgency at = this point, but it seems like the January 1 date is essentially an = arbitrary deadline without a clear connection to the support status of = CPython 2.7.</div><div class=3D""><br class=3D""></div><div class=3D"">Or = does anyone know a different way to reconcile these apparently = conflicting dates?</div><div class=3D""><br class=3D""></div><div = class=3D"">Jean-Paul</div></div></div></div></blockquote></div><br = class=3D""></body></html>= --Apple-Mail=_D5BE4171-1740-4024-9727-D5A98C74C67D-- --===============4131752959112036442== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVHdpc3RlZC1Q eXRob24gbWFpbGluZyBsaXN0ClR3aXN0ZWQtUHl0aG9uQHR3aXN0ZWRtYXRyaXguY29tCmh0dHBz Oi8vdHdpc3RlZG1hdHJpeC5jb20vY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3R3aXN0ZWQtcHl0 aG9uCg== --===============4131752959112036442==--