mirror of
https://github.com/python/cpython.git
synced 2025-11-03 03:22:27 +00:00
Fix misinformation about NaN != NaN comparison (GH-19357)
This commit is contained in:
parent
909f4a3009
commit
810f68f128
1 changed files with 3 additions and 2 deletions
|
|
@ -1422,8 +1422,9 @@ built-in types.
|
||||||
The not-a-number values ``float('NaN')`` and ``decimal.Decimal('NaN')`` are
|
The not-a-number values ``float('NaN')`` and ``decimal.Decimal('NaN')`` are
|
||||||
special. Any ordered comparison of a number to a not-a-number value is false.
|
special. Any ordered comparison of a number to a not-a-number value is false.
|
||||||
A counter-intuitive implication is that not-a-number values are not equal to
|
A counter-intuitive implication is that not-a-number values are not equal to
|
||||||
themselves. For example, if ``x = float('NaN')``, ``3 < x``, ``x < 3``, ``x
|
themselves. For example, if ``x = float('NaN')``, ``3 < x``, ``x < 3`` and
|
||||||
== x``, ``x != x`` are all false. This behavior is compliant with IEEE 754.
|
``x == x`` are all false, while ``x != x`` is true. This behavior is
|
||||||
|
compliant with IEEE 754.
|
||||||
|
|
||||||
* ``None`` and ``NotImplemented`` are singletons. :PEP:`8` advises that
|
* ``None`` and ``NotImplemented`` are singletons. :PEP:`8` advises that
|
||||||
comparisons for singletons should always be done with ``is`` or ``is not``,
|
comparisons for singletons should always be done with ``is`` or ``is not``,
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue