➜

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 serhiy.storchaka
Recipients Arfrever, alex, barry, docs@python, eric.snow, mark.dickinson, mjacob, ncoghlan, python-dev, rhettinger, serhiy.storchaka, vstinner
Date 2019-06-03.07:10:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559545851.95.0.630272206643.issue17576@roundup.psfhosted.org>
In-reply-to
Content 
> Can we at least switch to PyLong_CheckExact?

This is a behavior change and as such should be preceded by a period of warning.

If we go this way I propose to add a FutureWarning for int subclasses with overridden __index__.

As for turning the deprecated behaviour into TypeErrors, we added yet few deprecation warnings in 3.8. Would not be better to turn all of them into TypeErrors at the same time?
History
Date User Action Args
2019-06-03 07:10:51serhiy.storchakasetrecipients: + serhiy.storchaka, barry, rhettinger, mark.dickinson, ncoghlan, vstinner, Arfrever, alex, docs@python, python-dev, eric.snow, mjacob
2019-06-03 07:10:51serhiy.storchakasetmessageid: <1559545851.95.0.630272206643.issue17576@roundup.psfhosted.org>
2019-06-03 07:10:51serhiy.storchakalinkissue17576 messages
2019-06-03 07:10:51serhiy.storchakacreate