summaryrefslogtreecommitdiff
path: root/Python/ceval.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
commita84099bcc5cf9bba4bb6e14a296202a4fca5f106 (patch)
treed0c8c10ab099764a5ba43cc8f63a412cfe820a82 /Python/ceval.c
parent7aaa85932cf576470f2befe8257b29039b2cb411 (diff)
parent39430daa3b82a121b80633436170d0e0757f0fac (diff)
downloadcpython-git-a84099bcc5cf9bba4bb6e14a296202a4fca5f106.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/ceval.c')
0 files changed, 0 insertions, 0 deletions