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 steve.dower
Recipients mark.dickinson, steve.dower
Date 2021-12-09.16:37:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1639067876.07.0.133539744076.issue46018@roundup.psfhosted.org>
In-reply-to
Content
I considered just switching to <2.0, but wasn't sure if I would be breaking some other unspoken behaviour there. But you're right, it's really just detecting underflow vs. overflow, so that's a much simpler way to check.

I've filed the upstream report. I suspect the errno is coming from the exp() call within the expm1() implementation, so it's underflowing towards 0.0 and then subtracting 1.
History
Date User Action Args
2021-12-09 16:37:56steve.dowersetrecipients: + steve.dower, mark.dickinson
2021-12-09 16:37:56steve.dowersetmessageid: <1639067876.07.0.133539744076.issue46018@roundup.psfhosted.org>
2021-12-09 16:37:56steve.dowerlinkissue46018 messages
2021-12-09 16:37:56steve.dowercreate