Turn heaps library into a more OOP data structure?

[CrazyPython]

BPO	27290
Nosy	@rhettinger, @CrazyPython

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/rhettinger'
closed_at = <Date 2016-06-10.22:02:49.713>
created_at = <Date 2016-06-10.21:48:11.852>
labels = ['library']
title = 'Turn heaps library into a more OOP data structure?'
updated_at = <Date 2016-06-11.00:12:44.824>
user = 'https://github.com/CrazyPython'

bugs.python.org fields:

activity = <Date 2016-06-11.00:12:44.824>
actor = 'James.Lu'
assignee = 'rhettinger'
closed = True
closed_date = <Date 2016-06-10.22:02:49.713>
closer = 'rhettinger'
components = ['Library (Lib)']
creation = <Date 2016-06-10.21:48:11.852>
creator = 'James.Lu'
dependencies = []
files = []
hgrepos = []
issue_num = 27290
keywords = []
message_count = 3.0
messages = ['268159', '268161', '268170']
nosy_count = 2.0
nosy_names = ['rhettinger', 'James.Lu']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue27290'
versions = ['Python 3.6']

[CrazyPython]

The heapq library uses a list or other mutable sequence time to represent a heap. Since Python is a highly OOP language, why not make heaps their own data type?

[rhettinger]

The main reason is that there would be very little benefit. Lists are a very efficient data structure and the heap manipulations are also very cheap.

[CrazyPython]

Even a wrapper class would be helpful, it's simply more pythonic.

On Fri, Jun 10, 2016 at 6:02 PM, Raymond Hettinger <report@bugs.python.org>
wrote:

Raymond Hettinger added the comment:

The main reason is that there would be very little benefit. Lists are a
very efficient data structure and the heap manipulations are also very
cheap.

----------
assignee: -> rhettinger
nosy: +rhettinger
resolution: -> rejected
status: open -> closed

---

Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue27290\>

---