classification
Title: Add -3 warning for extension types that implement tp_compare but not tp_richcompare
Type: Stage:
Components: Versions: Python 2.7, Python 2.6
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: mark.dickinson, ncoghlan
Priority: normal Keywords:

Created on 2009-02-08 10:34 by mark.dickinson, last changed 2009-02-08 11:05 by mark.dickinson.

Messages (2)
msg81371 - (view) Author: Mark Dickinson (mark.dickinson) * (Python committer) Date: 2009-02-08 10:34
See

http://mail.python.org/pipermail/python-dev/2009-February/085809.html

where Nick Coghlan writes:

"I'm wondering if Mark should add the exception he recently removed back
in as a Deprecation Warning when tp_compare is defined, but
tp_richcompare is not. Such a warning should also be present when
running with -3 in 2.7 (assuming it isn't already there)."

A technical difficulty with adding this warning is that various built-in 
types implement tp_compare but not tp_richcompare.  For example:  int, 
long, slice, buffer, instancemethod, cell and bool all do this.
msg81372 - (view) Author: Mark Dickinson (mark.dickinson) * (Python committer) Date: 2009-02-08 11:05
N.B. The 3.x part of this was implemented in r69431 and r69432.
History
Date User Action Args
2009-02-08 11:05:48mark.dickinsonsetmessages: + msg81372
2009-02-08 10:34:14mark.dickinsoncreate