summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNed Deily <nad@acm.org>2013-07-16 02:07:41 (GMT)
committerNed Deily <nad@acm.org>2013-07-16 02:07:41 (GMT)
commitb7a285f5287fea77d1af477e83f46c8a44f910f3 (patch)
tree8ae9da1b146663c34c30694d12efdc17c9145f5a
parentc8ef9bc69471b3f5a789dad61d2330cf8193926c (diff)
downloadcpython-b7a285f5287fea77d1af477e83f46c8a44f910f3.zip
cpython-b7a285f5287fea77d1af477e83f46c8a44f910f3.tar.gz
cpython-b7a285f5287fea77d1af477e83f46c8a44f910f3.tar.bz2
Issue #18471: Fix typo in heapq documentation (reported by François Pinard).
-rw-r--r--Doc/library/heapq.rst2
1 files changed, 1 insertions, 1 deletions
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 :-).