From b7a285f5287fea77d1af477e83f46c8a44f910f3 Mon Sep 17 00:00:00 2001 From: Ned Deily Date: Mon, 15 Jul 2013 19:07:41 -0700 Subject: =?UTF-8?q?Issue=20#18471:=20Fix=20typo=20in=20heapq=20documentati?= =?UTF-8?q?on=20(reported=20by=20Fran=C3=A7ois=20Pinard).?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- Doc/library/heapq.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/library/heapq.rst b/Doc/library/heapq.rst index f0723b7..e8acd6c 100644 --- a/Doc/library/heapq.rst +++ b/Doc/library/heapq.rst @@ -260,7 +260,7 @@ A nice feature of this sort is that you can efficiently insert new items while the sort is going on, provided that the inserted items are not "better" than the last 0'th element you extracted. This is especially useful in simulation contexts, where the tree holds all incoming events, and the "win" condition -means the smallest scheduled time. When an event schedule other events for +means the smallest scheduled time. When an event schedules other events for execution, they are scheduled into the future, so they can easily go into the heap. So, a heap is a good structure for implementing schedulers (this is what I used for my MIDI sequencer :-). -- cgit v0.12