RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-March/098857.html below:

[Python-Dev] Why is nan != nan?

[Python-Dev] Why is nan != nan? [Python-Dev] Why is nan != nan?Alexander Belopolsky alexander.belopolsky at gmail.com
Wed Mar 24 23:52:38 CET 2010

Previous message: [Python-Dev] Why is nan != nan?
Next message: [Python-Dev] Why is nan != nan?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, Mar 24, 2010 at 6:47 PM, Mark Dickinson <dickinsm at gmail.com> wrote:
..
> There's no ideal solution here;  IMO, the compromise that currently
> exists is an acceptable one.

I don't see a compromise.   So far I failed to find a use case that
benefits from NaN violating reflexivity.

Previous message: [Python-Dev] Why is nan != nan?
Next message: [Python-Dev] Why is nan != nan?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-Dev mailing list

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