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 mark.dickinson
Recipients mark.dickinson, steve.dower
Date 2021-12-09.08:12:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639037553.87.0.862378591675.issue46018@roundup.psfhosted.org>
In-reply-to
Content
It's a bit cheap and nasty, but I think we could simply replace the line:

    if (fabs(x) < 1.0)

in is_error with

    if (fabs(x) < 2.0)

perhaps with an explanatory comment. All we need to do is distinguish underflow from overflow, and 2.0 is still clearly a _long_ way away from any overflow boundary.

It would be good to have a test that would trigger the behaviour, too.
History
Date User Action Args
2021-12-09 08:12:33mark.dickinsonsetrecipients: + mark.dickinson, steve.dower
2021-12-09 08:12:33mark.dickinsonsetmessageid: <1639037553.87.0.862378591675.issue46018@roundup.psfhosted.org>
2021-12-09 08:12:33mark.dickinsonlinkissue46018 messages
2021-12-09 08:12:33mark.dickinsoncreate