On 3/21/07, Greg Ewing <[EMAIL PROTECTED]> wrote: > In addition to this, what about the idea of a Python-level > __richcmp__ method? It would provide a single point of override > for classes that wanted to use it, and it shouldn't upset any > default behaviours since it's just exposing what's there > at the C level anyway.
I apologize if this is a silly question, but what would be the difference between the proposed __richcmp__ and the old __cmp__ that's being removed? -- Daniel Stutzbach, Ph.D. President, Stutzbach Enterprises LLC _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
