[issue4207] Remove backwards compatibility in _heapq for performance

2008-10-26 Thread Kristján Valur Jónsson
Kristján Valur Jónsson <[EMAIL PROTECTED]> added the comment: I am sorry for not doing my research about the age of the compatibility fix. However, modifying the test slightly to work with tuples of (random.random(), random.random()) shows a performance increase from: heapify 0.366187741738 pus

[issue4207] Remove backwards compatibility in _heapq for performance

2008-10-26 Thread Raymond Hettinger
Raymond Hettinger <[EMAIL PROTECTED]> added the comment: The compatability code was just added in Py2.6 and is needed for apps like Twisted that currently rely on __le__ being tested. In 3.0, the compatability code is removed and full speed is restored. Also, the timing suite exaggerates the ef

[issue4207] Remove backwards compatibility in _heapq for performance

2008-10-26 Thread Kristján Valur Jónsson
New submission from Kristján Valur Jónsson <[EMAIL PROTECTED]>: Comparing _heapq with our own legacy C implementation, blue.heapq at CCP, I noticed that ours was somewhat faster. I discovered that a lot of effort is being spent to dynamically search for a __lt__ operator, to provide backwards c