A blurb about the sort implementation.
This commit is contained in:
parent
2d8b765cc9
commit
f47630ff54
12
Misc/NEWS
12
Misc/NEWS
@ -6,6 +6,18 @@ Type/class unification and new-style classes
|
||||
|
||||
Core and builtins
|
||||
|
||||
- list.sort() has a new implementation. While cross-platform results
|
||||
may vary, and in data-dependent ways, this is much faster on many
|
||||
kinds of partially ordered lists than the previous implementation,
|
||||
and reported to be just as fast on randomly ordered lists on
|
||||
several major platforms. This sort is also stable (if A==B and A
|
||||
precedes B in the list at the start, A precedes B after the sort too),
|
||||
although the language definition does not guarantee stability. A
|
||||
potential drawback is that list.sort() may require temp space of
|
||||
len(list)*2 bytes (*4 on a 64-bit machine). It's therefore possible
|
||||
for list.sort() to raise MemoryError now, even if a comparison function
|
||||
does not. See <http://www.python.org/sf/587076> for full details.
|
||||
|
||||
- All standard iterators now ensure that, once StopIteration has been
|
||||
raised, all future calls to next() on the same iterator will also
|
||||
raise StopIteration. There used to be various counterexamples to
|
||||
|
Loading…
x
Reference in New Issue
Block a user