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 alex, belopolsky, daniel.urban, mark.dickinson, rhettinger
Date 2011-05-14.19:00:18
SpamBayes Score 7.37174e-05
Marked as misclassified No
Message-id <>
> 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.
Date User Action Args
2011-05-14 19:00:19mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, belopolsky, alex, daniel.urban
2011-05-14 19:00:18mark.dickinsonsetmessageid: <>
2011-05-14 19:00:18mark.dickinsonlinkissue11949 messages
2011-05-14 19:00:18mark.dickinsoncreate