Re: [IronPython] Rich comparison usage by IronPython's heapq implementation

2011-03-14 Thread Jeff Hardy
Regardless of what's "correct", we should follow what CPython does (plus, using only __lt__ and __eq__ makes sense). Can you try this in 2.7 to see if it's still an issue, and open a bug if it is? I doubt we'll make any more changes to 2.6. - Jeff On Mon, Mar 14, 2011 at 6:04 AM, Robert Smallshir

[IronPython] Rich comparison usage by IronPython's heapq implementation

2011-03-14 Thread Robert Smallshire
Hello, I recently ran into some issues with IronPython's heapq implementation whereby code that functions correctly on CPython failed with IronPython 2.6. The issue is that the CPython implementation of heapq only calls __le__() and __eq__() on the heap elements whereas the IronPython implementat