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 ncoghlan
Recipients jdemeyer, lukasz.langa, ncoghlan, petr.viktorin, scoder, steve.dower, vstinner, willingc
Date 2019-06-21.14:28:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561127290.79.0.926770829825.issue37250@roundup.psfhosted.org>
In-reply-to
Content
It isn't the actively maintained projects that publish wheel files that I'm worried about fixing - it's the sdist only projects that would otherwise only need recompilation to work on the new Python version.

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).

My opinion would be different if tp_print had actually been emitting compile time warnings for the past 10 years, but it hasn't been - we just haven't been using it for anything.
History
Date User Action Args
2019-06-21 14:28:10ncoghlansetrecipients: + ncoghlan, scoder, vstinner, petr.viktorin, lukasz.langa, jdemeyer, steve.dower, willingc
2019-06-21 14:28:10ncoghlansetmessageid: <1561127290.79.0.926770829825.issue37250@roundup.psfhosted.org>
2019-06-21 14:28:10ncoghlanlinkissue37250 messages
2019-06-21 14:28:10ncoghlancreate