From 815427c481fbef0f9110f4e3d3e4c2d9eebd64cd Mon Sep 17 00:00:00 2001 From: Guido van Rossum Date: Wed, 3 Dec 2008 15:24:50 +0000 Subject: [PATCH] Remove remark about NaN==NaN, I misunderstood that issue. --- Doc/whatsnew/3.0.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Doc/whatsnew/3.0.rst b/Doc/whatsnew/3.0.rst index a2afb32ffe4..169c87617f0 100644 --- a/Doc/whatsnew/3.0.rst +++ b/Doc/whatsnew/3.0.rst @@ -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 other. Note that this does not apply to the ``==`` and ``!=`` operators: objects of different incomparable types always compare - unequal to each other, and an object always compares equal to itself - (i.e., ``x is y`` implies ``x == y``; this is true even for *NaN*). + unequal to each other. * :meth:`builtin.sorted` and :meth:`list.sort` no longer accept the *cmp* argument providing a comparison function. Use the *key*