Ian Kelly wrote:
As far as I know nothing changed between 2.4 and 2.7 in this regard.
Python has always had NaN compare unequal to everything, per the
standard.
It might have been platform-specific in 2.4.
Okay, here's your problem: there isn't just one binary representation
for NaN.
I'm fully aware of that. Whether NaN's are one equivalence class or several is
not the issue. What matters is the integrity of the equivalence relation.
Following the standard isn't a good reason itself?
If a standard tells you to jump of a cliff...
regards, Anders
--
https://mail.python.org/mailman/listinfo/python-list
