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.17:05:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639069526.13.0.173222082528.issue36048@roundup.psfhosted.org>
In-reply-to
Content
Hi, I'm cculianu, the reporting user.

May I get a link or some background for the motivation for this change? It seems to me that there are vague allusions to "Decimal -> int cause problems in past", or some such, and I'd like to read the arguments presented as to what problems in particular, and how this change fixes those problems.

Mathematically, and by convention in computer science, conversions from float-like types -> int are always well defined.  It seems strangely un-Pythonic to restrict things in such a way.  I am very surprised by this change, quite frankly.  It's the wrong direction to go in, for this language, is my intuitive feeling.

Anyway, very curious about what the rationale was for this. Thanks.
History
Date User Action Args
2021-12-09 17:05:26calin.culianusetrecipients: + calin.culianu, gvanrossum, mark.dickinson, vstinner, serhiy.storchaka, hroncok, remi.lapeyre, arhadthedev
2021-12-09 17:05:26calin.culianusetmessageid: <1639069526.13.0.173222082528.issue36048@roundup.psfhosted.org>
2021-12-09 17:05:26calin.culianulinkissue36048 messages
2021-12-09 17:05:26calin.culianucreate