➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2009-02-08 10:34 by mark.dickinson, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg81371 - (view) | Author: Mark Dickinson (mark.dickinson) *  |
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) * |
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 |
| 2022-04-11 14:56:45 | admin | set | github: 49434 |
| 2020-05-31 12:30:25 | serhiy.storchaka | set | status: open -> closed resolution: out of date stage: resolved |
| 2012-11-03 15:40:20 | Ramchandra Apte | set | type: behavior |
| 2009-02-08 11:05:48 | mark.dickinson | set | messages: + msg81372 |
| 2009-02-08 10:34:14 | mark.dickinson | create | |