Raymond Hettinger <[EMAIL PROTECTED]> added the comment: I'll fix this to accommodate both cases, __lt__ and __le__. After trying x<y and finding the comparison isn't defined, it can try (not y<=x) instead.
Also, will document that either __cmp__ or all six rich comparisons should be defined for code that wants to run through sort, bisect, min/max, or heapq. The rich comparison PEP is clear on this point, but I don't think the affirmative statement ever made it to main docs: "The reflexivity rules *are* assumed by Python. Thus, the interpreter may swap y>x with x<y, y>=x with x<=y, and may swap the arguments of x==y and x!=y." -- PEP 207 ---------- priority: -> high _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3051> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
