Or if we are willing to make bigger changes to the module, there should be
a sort of class that can remember if it is supposed to represent a min-heap
or a max-heap. This has been discussed several times:
But nothing definite has come out of those discussions, as far as I can
On Tuesday, March 6, 2018 at 9:59:00 AM UTC-8, Neil Girdhar wrote:
> heapq creates and works with min-heaps. Currently, the only way to do
> this is to use _heapify_max instead of heapify, heapq._heappop_max instead
> of heapq.heappop, etc.
> These methods should be exposed using a reverse keyword argument rather
> than as private methods just like sort.
Python-ideas mailing list
Code of Conduct: http://python.org/psf/codeofconduct/