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 seberg
Recipients gregory.p.smith, lukasz.langa, mark.dickinson, miss-islington, seberg, tim.peters, twouters
Date 2021-08-04.18:21:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1628101296.33.0.350859925007.issue44698@roundup.psfhosted.org>
In-reply-to
Content
The fix broke NumPy (see also https://github.com/numpy/numpy/pull/19612)

It seems incorrect.  After all, it doesn't matter much whether the float can be converted to an integer correctly (or even if it returns an undefined value), so long `int_value == float_value` remains sensible.

The old cast cast integers to complex when they were out of range (which is fine), the new code raises an error instead.
History
Date User Action Args
2021-08-04 18:21:36sebergsetrecipients: + seberg, tim.peters, twouters, gregory.p.smith, mark.dickinson, lukasz.langa, miss-islington
2021-08-04 18:21:36sebergsetmessageid: <1628101296.33.0.350859925007.issue44698@roundup.psfhosted.org>
2021-08-04 18:21:36seberglinkissue44698 messages
2021-08-04 18:21:35sebergcreate