➜
See More

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 calin.culianu
Recipients arhadthedev, calin.culianu, gvanrossum, hroncok, mark.dickinson, remi.lapeyre, serhiy.storchaka, vstinner
Date 2021-12-09.20:32:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content 
Ok, Guido, thanks. Fair enough.

So regardless: what is the problem exactly if a C function expects an int but gets given a float? Why does such strictness matter, in that it required a whole other set of __index__ etc to be added?  I am having trouble seeing the actual problem, which was taken as a given in all the archaeology I have done on this ancient "issue" -- but is it a given?  There is no problem... only the one created by this change, really.
History
Date User Action Args
2021-12-09 20:32:01calin.culianusetrecipients: + calin.culianu, gvanrossum, mark.dickinson, vstinner, serhiy.storchaka, hroncok, remi.lapeyre, arhadthedev
2021-12-09 20:32:01calin.culianusetmessageid: <[email protected]>
2021-12-09 20:32:01calin.culianulinkissue36048 messages
2021-12-09 20:32:01calin.culianucreate