Re: The Python 2.7 Plan
Glyph <[email protected]> Mon, 16 Dec 2019 07:10:20 -0800
| Newsgroups | gmane.comp.python.twisted |
|---|---|
| Message-ID | <[email protected]> |
--===============0875415009153532322== Content-Type: multipart/alternative; boundary="Apple-Mail=_6330A2BC-8FA5-4D0D-AF35-AB5E593BC744" --Apple-Mail=_6330A2BC-8FA5-4D0D-AF35-AB5E593BC744 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > 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? This is just speculative, just based on my own historical understanding = of python-dev's process and somewhat informal definition of "support", = but I believe the sentence "Support officially stops January 1 2020, but = the final release will occur after that date." means something like "We = will accept new bug reports and may start fixing things until January 1; = however, the fixes in progress as of that date will be completed and = released in a final version some time later." 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. -g --Apple-Mail=_6330A2BC-8FA5-4D0D-AF35-AB5E593BC744 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 = dir=3D"auto" 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 = 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></div></div></blockquote><br = class=3D""></div><div>This is just speculative, just based on my own = historical understanding of python-dev's process and somewhat informal = definition of "support", but I believe the sentence "Support officially = stops January 1 2020, but the final release will occur after that date." = means something like "We will accept new bug reports and may <i = class=3D"">start</i> fixing things until January 1; however, the fixes = in progress as of that date will be completed and released in a final = version some time later."</div><div><br class=3D""></div><div>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><br = class=3D""></div><div>-g</div><br class=3D""></div></body></html>= --Apple-Mail=_6330A2BC-8FA5-4D0D-AF35-AB5E593BC744-- --===============0875415009153532322== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KVHdpc3RlZC1Q eXRob24gbWFpbGluZyBsaXN0ClR3aXN0ZWQtUHl0aG9uQHR3aXN0ZWRtYXRyaXguY29tCmh0dHBz Oi8vdHdpc3RlZG1hdHJpeC5jb20vY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL3R3aXN0ZWQtcHl0 aG9uCg== --===============0875415009153532322==--