[issue3051] heapq change breaking compatibility

[Raymond Hettinger]

Raymond Hettinger <rhettinger at users.sourceforge.net> added the comment:

Am closing this.  It would make no sense to change simple, pure python code to support objects implementing only one of the rich comparison methods.  People implementing rich comparisons need to implement all six if they want to guarantee total ordering and to be usable by various modules that need to be able to make comparisons.

FWIW, the C code is not guaranteed to be exactly the same in terms of implementation details, only the published API should be the same.  And, for this module, a decision was made for the C code to support only lists eventhough the pure python version supports any sequence.

----------
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3051>
_______________________________________