[issue11949] Make float('nan') unorderable
Mark Dickinson
report at bugs.python.org
Sat May 14 21:00:18 CEST 2011
Mark Dickinson <dickinsm at gmail.com> added the comment:
> Therefore making <, >, etc. raise on NaN while keeping the
> status quo for != and == would bring Python floats closer to
> compliance with IEEE 754.
Not so. Either way, Python would be providing exactly 10 of the 22 required IEEE 754 comparison operations (see sections 5.6.1 and 5.11 of IEEE 754-2008 for details). If we wanted to move closer to compliance with IEEE 754, we should be providing all 22 comparisons.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue11949>
_______________________________________
More information about the Python-bugs-list
mailing list