Author serhiy.storchaka
Recipients Arfrever, alex, barry, docs@python, eric.snow, mark.dickinson, mjacob, ncoghlan, python-dev, serhiy.storchaka, vstinner
Date 2019-06-02.11:11:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559473909.82.0.673703627215.issue17576@roundup.psfhosted.org>
In-reply-to
Content
I am not sure that raising an error is the best option. We can just convert an integer subclass to an exact int using _PyLong_Copy().

I am not sure that converting to an exact int in low-level C API functions is the best option. In many cases we use only the content of the resulting object ignoring its type (when convert it to the C integer or float, to bytes array, to new instance of int subclass). Creating a new exact int is a waste of time.

This is why I withdrawn my patches and this issue is still open.
History
Date User Action Args
2019-06-02 11:11:49serhiy.storchakasetrecipients: + serhiy.storchaka, barry, mark.dickinson, ncoghlan, vstinner, Arfrever, alex, docs@python, python-dev, eric.snow, mjacob
2019-06-02 11:11:49serhiy.storchakasetmessageid: <1559473909.82.0.673703627215.issue17576@roundup.psfhosted.org>
2019-06-02 11:11:49serhiy.storchakalinkissue17576 messages
2019-06-02 11:11:49serhiy.storchakacreate