Consolidate the logic for nlargest() into a single function.  Remove both the C and pure Python base underlying code. With all the logic in a single function, it only becomes necessary to create, store, and compare the data tuples when a need item is added to the heap.  This means that the rest of the comparisons (checking to see whether a new item needs to be added to the heap) can run faster and not need to create a (key, order, elem) tuple.The change reduces the number of tuples created and the number of ordering integers created.When rich comparisons were introduced, tuple ordering comparisons became twice as expensive (they are compared elementwise for equality and then there is an additional comparison call to order the first differing element).  Under the existing nlargest() code, we pay that price for every lement in the iterable.  In the new code, we pay that price only for the small subset of the iterable that actually gets added to the heap.After this, another patch for simplifying nsmallest() is forthcoming.

New changesetfadc06047314 by Raymond Hettinger in branch 'default':Issue#21424:  Optimize heaqp.nlargest() to make fewer tuple comparisons.http://hg.python.org/cpython/rev/fadc06047314

New changeset31950174f60f by Raymond Hettinger in branch 'default':Issue 21424:  Apply the nlargest() optimizations to nsmallest() as well.http://hg.python.org/cpython/rev/31950174f60f