[issue3051] heapq change breaking compatibility

[Maciek Fijalkowski]

Maciek Fijalkowski <fijal at genesilico.pl> added the comment:

I cannot honestly make much sense from what you said. My concern is whether python and C version behaves the same or not. It seems that in current version they intentionally behave differently, for simplicity and it's against policy of having the same functionality. I agree that it's an obscure corner case, but still.

----------

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