> >>> cmp(x,x) # x.__cmp__() is NOT called > 0 [Gustavo Niemeyer] > This is odd. We'll have problems trying to implemnt a NaN > following the convention of being not-equal to itself, > for example. That's what rich comparisons are for. There's no problem getting >>> x = some_nan >>> x = x False >>> in Python 2.4 (the result of that is *currently* a platform-dependent crapshoot, though). cmp(x, y) doesn't make sense for objects having only a partial ordering, so I don't care cmp() does with a NaN.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4