traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Remove remark about NaN==NaN, I misunderstood that issue.

This commit is contained in:
Guido van Rossum 2008-12-03 15:24:50 +00:00
parent ab4c51c2b3
commit 815427c481
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Doc/whatsnew/3.0.rst
View File

@ -182,8 +182,7 @@ Python 3.0 has simplified the rules for ordering comparisons:
no longer makes sense -- all the elements must be comparable to each no longer makes sense -- all the elements must be comparable to each
other. Note that this does not apply to the ``==`` and ``!=`` other. Note that this does not apply to the ``==`` and ``!=``
operators: objects of different incomparable types always compare operators: objects of different incomparable types always compare
unequal to each other, and an object always compares equal to itself unequal to each other.
(i.e., ``x is y`` implies ``x == y``; this is true even for *NaN*).
* :meth:`builtin.sorted` and :meth:`list.sort` no longer accept the * :meth:`builtin.sorted` and :meth:`list.sort` no longer accept the
*cmp* argument providing a comparison function. Use the *key* *cmp* argument providing a comparison function. Use the *key*