diff options
| author | Raymond Hettinger <python@rcn.com> | 2016-08-30 10:47:49 -0700 |
|---|---|---|
| committer | Raymond Hettinger <python@rcn.com> | 2016-08-30 10:47:49 -0700 |
| commit | 15f44ab043b37c064d6891c7864205fed9fb0dd1 (patch) | |
| tree | 726736587da36fbfebc1dfb12c4d9c14e6bf9a61 /Objects/listsort.txt | |
| parent | 613debcf0a0409b49ad4e1ee63dfc73119029755 (diff) | |
| download | cpython-git-15f44ab043b37c064d6891c7864205fed9fb0dd1.tar.gz | |
Issue #27895: Spelling fixes (Contributed by Ville Skyttä).
Diffstat (limited to 'Objects/listsort.txt')
| -rw-r--r-- | Objects/listsort.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Objects/listsort.txt b/Objects/listsort.txt index fef982f8a6..17d27973f8 100644 --- a/Objects/listsort.txt +++ b/Objects/listsort.txt @@ -694,7 +694,7 @@ search doesn't reduce the quadratic data movement costs. But in CPython's case, comparisons are extraordinarily expensive compared to moving data, and the details matter. Moving objects is just copying -pointers. Comparisons can be arbitrarily expensive (can invoke arbitary +pointers. Comparisons can be arbitrarily expensive (can invoke arbitrary user-supplied Python code), but even in simple cases (like 3 < 4) _all_ decisions are made at runtime: what's the type of the left comparand? the type of the right? do they need to be coerced to a common type? where's the |