summaryrefslogtreecommitdiff
path: root/Python/errors.c
diff options
context:
space:
mode:
authorEli Bendersky <eliben@gmail.com>2015-03-14 20:17:38 -0700
committerEli Bendersky <eliben@gmail.com>2015-03-14 20:17:38 -0700
commit38d6e0f84a4c1f23b6fba04b71b5f5dc3a6f305a (patch)
tree068d8fd5b68b3cd93a1d04f04202469100d4c6b2 /Python/errors.c
parent14e1dfbfbd25c36f7c8b6bf869bfd3f9a819a479 (diff)
parent492ed42f72c952ba9b916c010af1ebcc68cccd71 (diff)
downloadcpython-38d6e0f84a4c1f23b6fba04b71b5f5dc3a6f305a.tar.gz
Issue #23549: Clarify confusion in heapq doc - accessing the mininmal element
Merge 3.4 The current documentation only mentions heap[0] as the smallest element in the beginning, and not in any of the methods' docs. There's no method to access the minimal element without popping it, and the documentation of nsmallest is confusing because it may suggest that min() is the way to go for n==1.
Diffstat (limited to 'Python/errors.c')
0 files changed, 0 insertions, 0 deletions