A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] Why is nan != nan? [Python-Dev] Why is nan != nan?Mark Dickinson dickinsm at gmail.com
Thu Mar 25 00:02:39 CET 2010 
On Wed, Mar 24, 2010 at 10:52 PM, Alexander Belopolsky
<alexander.belopolsky at gmail.com> wrote:
> 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.
>

So if I understand correctly, you propose that float('nan') ==
float('nan') return True.  Would you also suggest extending this
behaviour to Decimal nans?
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