Why is bool(float("nan")) == True?

[EarthAndMoon]

Why is

1	bool(float("nan")) == True

?

[deanhystad]

bool(float_value) is True for all float values != 0.0. nan does not equal 0.0

[philipyip]

The bool class can be used to type cast a string into a bool. An empty string will return False:

1 2	empty_string = '' bool(empty_string)

A non-empty string returns True:

1 2	non_empty_string = 'nan' bool(non_empty_string)

The bool class can be used to type cast a float into a bool. A float of value 0.0 will return False:

1

bool(0.0)

Any other float returns True:

1 2	bool(0.1) bool(float('nan'))

And the following is True:

1	float('nan') != 0.0

[DeaD_EyE]

The documentation is interesting and also telling some facts about the C99 Standard.

https://docs.python.org/3/library/math.h...n#math.nan

A floating-point “not a number” (NaN) value. Equivalent to the output of float('nan'). Due to the requirements of the IEEE-754 standard, math.nan and float('nan') are not considered to equal to any other numeric value, including themselves. To check whether a number is a NaN, use the isnan() function to test for NaNs instead of is or ==. Example:

One solution to get a False could be:

1 2 3 4

import math     result = not math.isnan(float("nan"))

[Gribouillis]

Due to the requirements of the IEEE-754 standard, math.nan and float('nan') are not considered to equal to any other numeric value, including themselves.

1 2 3 4 5 6 7

>>> float('nan') == float('nan') False >>> >>> x = float('nan') >>> x == x False >>>

That's because you can never tell where a NaN value comes from, and the IEEE-754 format allows several NaN values.