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

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

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

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

On Fri, Mar 26, 2010 at 17:16, Raymond Hettinger
<raymond.hettinger at gmail.com> wrote:
> Of the ideas I've seen in this thread, only two look reasonable:
> * Do nothing.  This is attractive because it doesn't break anything.
> * Have float.__eq__(x, y) return True whenever x and y are
>    the same NaN object.  This is attractive because it is a
>    minimal change that provides a little protection for
>    simple containers.
> I support either of those options.

What's the flaw in using isnan()?


-- 
Adam Olsen, aka Rhamphoryncus

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

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