From: Guido van Rossum <guido@python.org>
Date: Thu, 18 Oct 2001 19:20:25 +0000 (+0000)
Subject: Note stricter tp_compare return value requirements.
X-Git-Tag: v2.2.1c1~1183
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=6c4bce3b5c843be20980aa082ac0ecc027b7ad58;p=thirdparty%2FPython%2Fcpython.git

Note stricter tp_compare return value requirements.
---

diff --git a/Misc/NEWS b/Misc/NEWS
index a91b7afec4cf..6d6c65928faa 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -103,6 +103,12 @@ Build
 
 C API
 
+- The documentation for the tp_compare slot is updated to require that
+  the return value must be -1, 0, 1; an arbitrary number <0 or >0 is
+  not correct.  This is not yet enforced but will be enforced in
+  Python 2.3; even later, we may use -2 to indicate errors and +2 for
+  "NotImplemented".  Right now, -1 should be used for an error return.
+
 - PyLong_AsLongLong() now accepts int (as well as long) arguments.
   Consequently, PyArg_ParseTuple's 'L' code also accepts int (as well
   as long) arguments.