This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients jdemeyer, lukasz.langa, ncoghlan, petr.viktorin, scoder, steve.dower, vstinner, willingc
Date 2019-06-21.14:39:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561127946.14.0.146006351547.issue37250@roundup.psfhosted.org>
In-reply-to
Content
> With this fixed, and the PyCode_New -> PyCode_New + PyCode_WithPosArgs fix from bpo-37221 merged, then that long tail will get another few years of life, and will start emitting deprecation warnings for the part that's actually going to go away in Python 3.9 (i.e. the tp_print slot).

By definition (as unmaintained packages), that's a few more years until death. Nobody is looking at their compile time warnings (that would require maintenance ;) ), so nothing will happen until it actually breaks. Keeping the field for one more version makes less sense than keeping it forever.
History
Date User Action Args
2019-06-21 14:39:06steve.dowersetrecipients: + steve.dower, ncoghlan, scoder, vstinner, petr.viktorin, lukasz.langa, jdemeyer, willingc
2019-06-21 14:39:06steve.dowersetmessageid: <1561127946.14.0.146006351547.issue37250@roundup.psfhosted.org>
2019-06-21 14:39:06steve.dowerlinkissue37250 messages
2019-06-21 14:39:06steve.dowercreate