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

Alexander Belopolsky alexander.belopolsky at gmail.com
Wed Mar 24 23:52:38 CET 2010


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.


More information about the Python-Dev mailing list