On Thu, Apr 28, 2011 at 1:40 AM, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
..
> The Pythonic thing to do (in the Python 3 world at least) would
> be to regard NaNs as non-comparable and raise an exception.
As I mentioned in a previous post, I agree in case of <, <=, >, or >=
comparisons, but == and != are a harder case because you don't want,
for example:
>>> [1,2,float('nan'),3].index(3)
3
to raise an exception.
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