Mark Dickinson added the comment: > we should perhaps produce the right sign bit for each
Perhaps. But given that signs of NaNs are pretty much meaningless anyway (the IEEE 754 standard explicitly refuses to attach any meaning to NaN sign bits, and the sign bit of a NaN result is not specified for most operations), and that a change *could* conceivably break existing code, I don't see much of a case for changing the behaviour in 2.7. I'm not particularly *opposed* to such a change; I just don't really see the point. BTW, I'd expect this report to apply to other platforms in addition to Windows; Intel's "default" NaN has its sign bit set, so a platform that just does the lazy thing and lets the FPU NaN propagate will tend to see an inverted sign bit here. It's only the 2.7 behaviour you're complaining about, right? Are things working as expected on 3.4 and Windows? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22590> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
