[Python-Dev] Why is nan != nan?
rhamph at gmail.com
Sat Mar 27 19:36:27 CET 2010
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
More information about the Python-Dev