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 Michael.Felt, mark.dickinson, vstinner
Date 2020-01-20.19:21:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579548074.44.0.292329240591.issue39396@roundup.psfhosted.org>
In-reply-to
Content
> Mark: what's your call on that one?

I don't know. It's a hard problem in general: where do we draw the line between simply wrapping the platform libm, bugs and all, on one hand and trying to abstract away platform differences and make guarantees about corner-case behaviour on the other.

For this particular case, I'd be fine with adding a special case for `x == y` in the code (suitably commented to explain why the special case is there, and under what conditions it can be removed). But I fear it's the thin end of the wedge: as Michael's last message shows, to get the test suite to pass on his particular flavour of AIX, we'd need to add a special case for cmath.exp, too, and there may be more failures once that's fixed.

Actually, the cmath.exp failure looks a little odd to my eyes: it would be a bit surprising to have cmath.exp fail if all of test_math passed. I suspect a dodgy compiler optimisation. But that's another issue.
History
Date User Action Args
2020-01-20 19:21:14mark.dickinsonsetrecipients: + mark.dickinson, vstinner, Michael.Felt
2020-01-20 19:21:14mark.dickinsonsetmessageid: <1579548074.44.0.292329240591.issue39396@roundup.psfhosted.org>
2020-01-20 19:21:14mark.dickinsonlinkissue39396 messages
2020-01-20 19:21:13mark.dickinsoncreate