2010-11-05 04:10:41 -03:00
|
|
|
.. _sortinghowto:
|
|
|
|
|
2024-02-20 03:51:56 -04:00
|
|
|
Sorting Techniques
|
|
|
|
******************
|
2010-09-01 06:15:42 -03:00
|
|
|
|
|
|
|
:Author: Andrew Dalke and Raymond Hettinger
|
|
|
|
|
|
|
|
|
|
|
|
Python lists have a built-in :meth:`list.sort` method that modifies the list
|
2011-01-12 00:44:41 -04:00
|
|
|
in-place. There is also a :func:`sorted` built-in function that builds a new
|
|
|
|
sorted list from an iterable.
|
2010-09-01 06:15:42 -03:00
|
|
|
|
|
|
|
In this document, we explore the various techniques for sorting data using Python.
|
|
|
|
|
|
|
|
|
|
|
|
Sorting Basics
|
|
|
|
==============
|
|
|
|
|
|
|
|
A simple ascending sort is very easy: just call the :func:`sorted` function. It
|
2021-04-19 18:12:36 -03:00
|
|
|
returns a new sorted list:
|
|
|
|
|
|
|
|
.. doctest::
|
2010-09-01 06:15:42 -03:00
|
|
|
|
|
|
|
>>> sorted([5, 2, 3, 1, 4])
|
|
|
|
[1, 2, 3, 4, 5]
|
|
|
|
|
2011-02-06 02:11:29 -04:00
|
|
|
You can also use the :meth:`list.sort` method. It modifies the list
|
2016-10-19 10:29:26 -03:00
|
|
|
in-place (and returns ``None`` to avoid confusion). Usually it's less convenient
|
2010-09-01 06:15:42 -03:00
|
|
|
than :func:`sorted` - but if you don't need the original list, it's slightly
|
|
|
|
more efficient.
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> a = [5, 2, 3, 1, 4]
|
|
|
|
>>> a.sort()
|
|
|
|
>>> a
|
|
|
|
[1, 2, 3, 4, 5]
|
|
|
|
|
|
|
|
Another difference is that the :meth:`list.sort` method is only defined for
|
|
|
|
lists. In contrast, the :func:`sorted` function accepts any iterable.
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> sorted({1: 'D', 2: 'B', 3: 'B', 4: 'E', 5: 'A'})
|
|
|
|
[1, 2, 3, 4, 5]
|
|
|
|
|
|
|
|
Key Functions
|
|
|
|
=============
|
|
|
|
|
2024-09-27 21:19:44 -03:00
|
|
|
The :meth:`list.sort` method and the functions :func:`sorted`,
|
|
|
|
:func:`min`, :func:`max`, :func:`heapq.nsmallest`, and
|
|
|
|
:func:`heapq.nlargest` have a *key* parameter to specify a function (or
|
|
|
|
other callable) to be called on each list element prior to making
|
2020-01-25 18:18:58 -04:00
|
|
|
comparisons.
|
2010-09-01 06:15:42 -03:00
|
|
|
|
2024-09-27 21:19:44 -03:00
|
|
|
For example, here's a case-insensitive string comparison using
|
|
|
|
:meth:`str.casefold`:
|
2010-09-01 06:15:42 -03:00
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2024-02-19 23:22:07 -04:00
|
|
|
>>> sorted("This is a test string from Andrew".split(), key=str.casefold)
|
2010-09-01 06:15:42 -03:00
|
|
|
['a', 'Andrew', 'from', 'is', 'string', 'test', 'This']
|
|
|
|
|
2020-01-25 18:18:58 -04:00
|
|
|
The value of the *key* parameter should be a function (or other callable) that
|
|
|
|
takes a single argument and returns a key to use for sorting purposes. This
|
|
|
|
technique is fast because the key function is called exactly once for each
|
|
|
|
input record.
|
2010-09-01 06:15:42 -03:00
|
|
|
|
|
|
|
A common pattern is to sort complex objects using some of the object's indices
|
|
|
|
as keys. For example:
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> student_tuples = [
|
2016-08-09 18:47:04 -03:00
|
|
|
... ('john', 'A', 15),
|
|
|
|
... ('jane', 'B', 12),
|
|
|
|
... ('dave', 'B', 10),
|
|
|
|
... ]
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> sorted(student_tuples, key=lambda student: student[2]) # sort by age
|
|
|
|
[('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]
|
|
|
|
|
|
|
|
The same technique works for objects with named attributes. For example:
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> class Student:
|
2016-08-09 18:47:04 -03:00
|
|
|
... def __init__(self, name, grade, age):
|
|
|
|
... self.name = name
|
|
|
|
... self.grade = grade
|
|
|
|
... self.age = age
|
|
|
|
... def __repr__(self):
|
|
|
|
... return repr((self.name, self.grade, self.age))
|
2010-09-01 06:15:42 -03:00
|
|
|
|
|
|
|
>>> student_objects = [
|
2016-08-09 18:47:04 -03:00
|
|
|
... Student('john', 'A', 15),
|
|
|
|
... Student('jane', 'B', 12),
|
|
|
|
... Student('dave', 'B', 10),
|
|
|
|
... ]
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> sorted(student_objects, key=lambda student: student.age) # sort by age
|
|
|
|
[('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]
|
|
|
|
|
2024-02-19 23:22:07 -04:00
|
|
|
Objects with named attributes can be made by a regular class as shown
|
|
|
|
above, or they can be instances of :class:`~dataclasses.dataclass` or
|
|
|
|
a :term:`named tuple`.
|
2010-09-01 06:15:42 -03:00
|
|
|
|
2024-02-19 23:22:07 -04:00
|
|
|
Operator Module Functions and Partial Function Evaluation
|
|
|
|
=========================================================
|
|
|
|
|
|
|
|
The :term:`key function` patterns shown above are very common, so Python provides
|
2011-02-06 02:11:29 -04:00
|
|
|
convenience functions to make accessor functions easier and faster. The
|
|
|
|
:mod:`operator` module has :func:`~operator.itemgetter`,
|
2012-04-29 13:32:30 -03:00
|
|
|
:func:`~operator.attrgetter`, and a :func:`~operator.methodcaller` function.
|
2010-09-01 06:15:42 -03:00
|
|
|
|
|
|
|
Using those functions, the above examples become simpler and faster:
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> from operator import itemgetter, attrgetter
|
|
|
|
|
|
|
|
>>> sorted(student_tuples, key=itemgetter(2))
|
|
|
|
[('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]
|
|
|
|
|
|
|
|
>>> sorted(student_objects, key=attrgetter('age'))
|
|
|
|
[('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]
|
|
|
|
|
|
|
|
The operator module functions allow multiple levels of sorting. For example, to
|
|
|
|
sort by *grade* then by *age*:
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> sorted(student_tuples, key=itemgetter(1,2))
|
|
|
|
[('john', 'A', 15), ('dave', 'B', 10), ('jane', 'B', 12)]
|
|
|
|
|
|
|
|
>>> sorted(student_objects, key=attrgetter('grade', 'age'))
|
|
|
|
[('john', 'A', 15), ('dave', 'B', 10), ('jane', 'B', 12)]
|
|
|
|
|
2024-02-19 23:22:07 -04:00
|
|
|
The :mod:`functools` module provides another helpful tool for making
|
|
|
|
key-functions. The :func:`~functools.partial` function can reduce the
|
|
|
|
`arity <https://en.wikipedia.org/wiki/Arity>`_ of a multi-argument
|
|
|
|
function making it suitable for use as a key-function.
|
|
|
|
|
|
|
|
.. doctest::
|
|
|
|
|
|
|
|
>>> from functools import partial
|
|
|
|
>>> from unicodedata import normalize
|
|
|
|
|
|
|
|
>>> names = 'Zoë Åbjørn Núñez Élana Zeke Abe Nubia Eloise'.split()
|
|
|
|
|
|
|
|
>>> sorted(names, key=partial(normalize, 'NFD'))
|
|
|
|
['Abe', 'Åbjørn', 'Eloise', 'Élana', 'Nubia', 'Núñez', 'Zeke', 'Zoë']
|
|
|
|
|
|
|
|
>>> sorted(names, key=partial(normalize, 'NFC'))
|
|
|
|
['Abe', 'Eloise', 'Nubia', 'Núñez', 'Zeke', 'Zoë', 'Åbjørn', 'Élana']
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
Ascending and Descending
|
|
|
|
========================
|
|
|
|
|
|
|
|
Both :meth:`list.sort` and :func:`sorted` accept a *reverse* parameter with a
|
2012-04-29 13:32:30 -03:00
|
|
|
boolean value. This is used to flag descending sorts. For example, to get the
|
2010-09-01 06:15:42 -03:00
|
|
|
student data in reverse *age* order:
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> sorted(student_tuples, key=itemgetter(2), reverse=True)
|
|
|
|
[('john', 'A', 15), ('jane', 'B', 12), ('dave', 'B', 10)]
|
|
|
|
|
|
|
|
>>> sorted(student_objects, key=attrgetter('age'), reverse=True)
|
|
|
|
[('john', 'A', 15), ('jane', 'B', 12), ('dave', 'B', 10)]
|
|
|
|
|
|
|
|
Sort Stability and Complex Sorts
|
|
|
|
================================
|
|
|
|
|
|
|
|
Sorts are guaranteed to be `stable
|
2016-02-26 14:37:12 -04:00
|
|
|
<https://en.wikipedia.org/wiki/Sorting_algorithm#Stability>`_\. That means that
|
2010-09-01 06:15:42 -03:00
|
|
|
when multiple records have the same key, their original order is preserved.
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> data = [('red', 1), ('blue', 1), ('red', 2), ('blue', 2)]
|
|
|
|
>>> sorted(data, key=itemgetter(0))
|
|
|
|
[('blue', 1), ('blue', 2), ('red', 1), ('red', 2)]
|
|
|
|
|
|
|
|
Notice how the two records for *blue* retain their original order so that
|
|
|
|
``('blue', 1)`` is guaranteed to precede ``('blue', 2)``.
|
|
|
|
|
|
|
|
This wonderful property lets you build complex sorts in a series of sorting
|
|
|
|
steps. For example, to sort the student data by descending *grade* and then
|
|
|
|
ascending *age*, do the *age* sort first and then sort again using *grade*:
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> s = sorted(student_objects, key=attrgetter('age')) # sort on secondary key
|
|
|
|
>>> sorted(s, key=attrgetter('grade'), reverse=True) # now sort on primary key, descending
|
|
|
|
[('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]
|
|
|
|
|
2018-10-20 18:39:03 -03:00
|
|
|
This can be abstracted out into a wrapper function that can take a list and
|
|
|
|
tuples of field and order to sort them on multiple passes.
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2018-10-20 18:39:03 -03:00
|
|
|
>>> def multisort(xs, specs):
|
|
|
|
... for key, reverse in reversed(specs):
|
|
|
|
... xs.sort(key=attrgetter(key), reverse=reverse)
|
|
|
|
... return xs
|
|
|
|
|
|
|
|
>>> multisort(list(student_objects), (('grade', True), ('age', False)))
|
|
|
|
[('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]
|
|
|
|
|
2016-02-26 14:37:12 -04:00
|
|
|
The `Timsort <https://en.wikipedia.org/wiki/Timsort>`_ algorithm used in Python
|
2010-09-01 06:15:42 -03:00
|
|
|
does multiple sorts efficiently because it can take advantage of any ordering
|
|
|
|
already present in a dataset.
|
|
|
|
|
2022-10-16 16:34:25 -03:00
|
|
|
Decorate-Sort-Undecorate
|
|
|
|
========================
|
2010-09-01 06:15:42 -03:00
|
|
|
|
|
|
|
This idiom is called Decorate-Sort-Undecorate after its three steps:
|
|
|
|
|
|
|
|
* First, the initial list is decorated with new values that control the sort order.
|
|
|
|
|
|
|
|
* Second, the decorated list is sorted.
|
|
|
|
|
|
|
|
* Finally, the decorations are removed, creating a list that contains only the
|
|
|
|
initial values in the new order.
|
|
|
|
|
|
|
|
For example, to sort the student data by *grade* using the DSU approach:
|
|
|
|
|
2024-02-19 23:22:07 -04:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> decorated = [(student.grade, i, student) for i, student in enumerate(student_objects)]
|
|
|
|
>>> decorated.sort()
|
|
|
|
>>> [student for grade, i, student in decorated] # undecorate
|
|
|
|
[('john', 'A', 15), ('jane', 'B', 12), ('dave', 'B', 10)]
|
|
|
|
|
|
|
|
This idiom works because tuples are compared lexicographically; the first items
|
|
|
|
are compared; if they are the same then the second items are compared, and so
|
|
|
|
on.
|
|
|
|
|
|
|
|
It is not strictly necessary in all cases to include the index *i* in the
|
|
|
|
decorated list, but including it gives two benefits:
|
|
|
|
|
|
|
|
* The sort is stable -- if two items have the same key, their order will be
|
|
|
|
preserved in the sorted list.
|
|
|
|
|
|
|
|
* The original items do not have to be comparable because the ordering of the
|
|
|
|
decorated tuples will be determined by at most the first two items. So for
|
|
|
|
example the original list could contain complex numbers which cannot be sorted
|
|
|
|
directly.
|
|
|
|
|
|
|
|
Another name for this idiom is
|
2016-02-26 14:37:12 -04:00
|
|
|
`Schwartzian transform <https://en.wikipedia.org/wiki/Schwartzian_transform>`_\,
|
2010-09-01 06:15:42 -03:00
|
|
|
after Randal L. Schwartz, who popularized it among Perl programmers.
|
|
|
|
|
|
|
|
Now that Python sorting provides key-functions, this technique is not often needed.
|
|
|
|
|
2022-10-16 16:34:25 -03:00
|
|
|
Comparison Functions
|
|
|
|
====================
|
2010-09-01 06:15:42 -03:00
|
|
|
|
2022-10-16 16:34:25 -03:00
|
|
|
Unlike key functions that return an absolute value for sorting, a comparison
|
|
|
|
function computes the relative ordering for two inputs.
|
2021-04-19 18:12:36 -03:00
|
|
|
|
2022-10-16 16:34:25 -03:00
|
|
|
For example, a `balance scale
|
|
|
|
<https://upload.wikimedia.org/wikipedia/commons/1/17/Balance_à_tabac_1850.JPG>`_
|
|
|
|
compares two samples giving a relative ordering: lighter, equal, or heavier.
|
|
|
|
Likewise, a comparison function such as ``cmp(a, b)`` will return a negative
|
|
|
|
value for less-than, zero if the inputs are equal, or a positive value for
|
|
|
|
greater-than.
|
2021-04-19 18:12:36 -03:00
|
|
|
|
2022-10-16 16:34:25 -03:00
|
|
|
It is common to encounter comparison functions when translating algorithms from
|
|
|
|
other languages. Also, some libraries provide comparison functions as part of
|
|
|
|
their API. For example, :func:`locale.strcoll` is a comparison function.
|
2016-08-09 18:47:04 -03:00
|
|
|
|
2022-10-16 16:34:25 -03:00
|
|
|
To accommodate those situations, Python provides
|
|
|
|
:class:`functools.cmp_to_key` to wrap the comparison function
|
|
|
|
to make it usable as a key function::
|
2010-09-01 06:15:42 -03:00
|
|
|
|
2022-10-31 14:58:13 -03:00
|
|
|
sorted(words, key=cmp_to_key(strcoll)) # locale-aware sort order
|
2010-09-01 06:15:42 -03:00
|
|
|
|
2024-09-27 21:19:44 -03:00
|
|
|
Strategies For Unorderable Types and Values
|
|
|
|
===========================================
|
|
|
|
|
|
|
|
A number of type and value issues can arise when sorting.
|
|
|
|
Here are some strategies that can help:
|
|
|
|
|
|
|
|
* Convert non-comparable input types to strings prior to sorting:
|
|
|
|
|
|
|
|
.. doctest::
|
|
|
|
|
|
|
|
>>> data = ['twelve', '11', 10]
|
|
|
|
>>> sorted(map(str, data))
|
|
|
|
['10', '11', 'twelve']
|
|
|
|
|
|
|
|
This is needed because most cross-type comparisons raise a
|
|
|
|
:exc:`TypeError`.
|
|
|
|
|
|
|
|
* Remove special values prior to sorting:
|
|
|
|
|
|
|
|
.. doctest::
|
|
|
|
|
|
|
|
>>> from math import isnan
|
|
|
|
>>> from itertools import filterfalse
|
|
|
|
>>> data = [3.3, float('nan'), 1.1, 2.2]
|
|
|
|
>>> sorted(filterfalse(isnan, data))
|
|
|
|
[1.1, 2.2, 3.3]
|
|
|
|
|
|
|
|
This is needed because the `IEEE-754 standard
|
|
|
|
<https://en.wikipedia.org/wiki/IEEE_754>`_ specifies that, "Every NaN
|
|
|
|
shall compare unordered with everything, including itself."
|
|
|
|
|
|
|
|
Likewise, ``None`` can be stripped from datasets as well:
|
|
|
|
|
|
|
|
.. doctest::
|
|
|
|
|
|
|
|
>>> data = [3.3, None, 1.1, 2.2]
|
|
|
|
>>> sorted(x for x in data if x is not None)
|
|
|
|
[1.1, 2.2, 3.3]
|
|
|
|
|
|
|
|
This is needed because ``None`` is not comparable to other types.
|
|
|
|
|
|
|
|
* Convert mapping types into sorted item lists before sorting:
|
|
|
|
|
|
|
|
.. doctest::
|
|
|
|
|
|
|
|
>>> data = [{'a': 1}, {'b': 2}]
|
|
|
|
>>> sorted(data, key=lambda d: sorted(d.items()))
|
|
|
|
[{'a': 1}, {'b': 2}]
|
|
|
|
|
|
|
|
This is needed because dict-to-dict comparisons raise a
|
|
|
|
:exc:`TypeError`.
|
|
|
|
|
|
|
|
* Convert set types into sorted lists before sorting:
|
|
|
|
|
|
|
|
.. doctest::
|
|
|
|
|
|
|
|
>>> data = [{'a', 'b', 'c'}, {'b', 'c', 'd'}]
|
|
|
|
>>> sorted(map(sorted, data))
|
|
|
|
[['a', 'b', 'c'], ['b', 'c', 'd']]
|
|
|
|
|
|
|
|
This is needed because the elements contained in set types do not have a
|
|
|
|
deterministic order. For example, ``list({'a', 'b'})`` may produce
|
|
|
|
either ``['a', 'b']`` or ``['b', 'a']``.
|
|
|
|
|
2022-05-04 00:38:29 -03:00
|
|
|
Odds and Ends
|
|
|
|
=============
|
2010-09-01 06:15:42 -03:00
|
|
|
|
|
|
|
* For locale aware sorting, use :func:`locale.strxfrm` for a key function or
|
2022-10-16 16:34:25 -03:00
|
|
|
:func:`locale.strcoll` for a comparison function. This is necessary
|
|
|
|
because "alphabetical" sort orderings can vary across cultures even
|
|
|
|
if the underlying alphabet is the same.
|
2010-09-01 06:15:42 -03:00
|
|
|
|
2011-02-06 02:11:29 -04:00
|
|
|
* The *reverse* parameter still maintains sort stability (so that records with
|
2010-09-01 06:15:42 -03:00
|
|
|
equal keys retain the original order). Interestingly, that effect can be
|
|
|
|
simulated without the parameter by using the builtin :func:`reversed` function
|
|
|
|
twice:
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> data = [('red', 1), ('blue', 1), ('red', 2), ('blue', 2)]
|
2016-04-26 05:11:10 -03:00
|
|
|
>>> standard_way = sorted(data, key=itemgetter(0), reverse=True)
|
|
|
|
>>> double_reversed = list(reversed(sorted(reversed(data), key=itemgetter(0))))
|
|
|
|
>>> assert standard_way == double_reversed
|
|
|
|
>>> standard_way
|
|
|
|
[('red', 1), ('red', 2), ('blue', 1), ('blue', 2)]
|
2010-09-01 06:15:42 -03:00
|
|
|
|
2022-04-29 19:08:07 -03:00
|
|
|
* The sort routines use ``<`` when making comparisons
|
2010-09-01 06:15:42 -03:00
|
|
|
between two objects. So, it is easy to add a standard sort order to a class by
|
2023-07-23 06:23:44 -03:00
|
|
|
defining an :meth:`~object.__lt__` method:
|
2021-04-19 18:12:36 -03:00
|
|
|
|
|
|
|
.. doctest::
|
2010-09-01 06:15:42 -03:00
|
|
|
|
|
|
|
>>> Student.__lt__ = lambda self, other: self.age < other.age
|
|
|
|
>>> sorted(student_objects)
|
|
|
|
[('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]
|
|
|
|
|
2023-07-23 06:23:44 -03:00
|
|
|
However, note that ``<`` can fall back to using :meth:`~object.__gt__` if
|
2024-02-19 23:22:07 -04:00
|
|
|
:meth:`~object.__lt__` is not implemented (see :func:`object.__lt__`
|
|
|
|
for details on the mechanics). To avoid surprises, :pep:`8`
|
|
|
|
recommends that all six comparison methods be implemented.
|
|
|
|
The :func:`~functools.total_ordering` decorator is provided to make that
|
|
|
|
task easier.
|
2022-04-29 19:08:07 -03:00
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
* Key functions need not depend directly on the objects being sorted. A key
|
|
|
|
function can also access external resources. For instance, if the student grades
|
|
|
|
are stored in a dictionary, they can be used to sort a separate list of student
|
|
|
|
names:
|
|
|
|
|
2021-04-19 18:12:36 -03:00
|
|
|
.. doctest::
|
|
|
|
|
2010-09-01 06:15:42 -03:00
|
|
|
>>> students = ['dave', 'john', 'jane']
|
|
|
|
>>> newgrades = {'john': 'F', 'jane':'A', 'dave': 'C'}
|
|
|
|
>>> sorted(students, key=newgrades.__getitem__)
|
|
|
|
['jane', 'dave', 'john']
|
2024-02-19 23:22:07 -04:00
|
|
|
|
|
|
|
Partial Sorts
|
|
|
|
=============
|
|
|
|
|
|
|
|
Some applications require only some of the data to be ordered. The standard
|
|
|
|
library provides several tools that do less work than a full sort:
|
|
|
|
|
|
|
|
* :func:`min` and :func:`max` return the smallest and largest values,
|
|
|
|
respectively. These functions make a single pass over the input data and
|
|
|
|
require almost no auxiliary memory.
|
|
|
|
|
|
|
|
* :func:`heapq.nsmallest` and :func:`heapq.nlargest` return
|
|
|
|
the *n* smallest and largest values, respectively. These functions
|
|
|
|
make a single pass over the data keeping only *n* elements in memory
|
|
|
|
at a time. For values of *n* that are small relative to the number of
|
|
|
|
inputs, these functions make far fewer comparisons than a full sort.
|
|
|
|
|
|
|
|
* :func:`heapq.heappush` and :func:`heapq.heappop` create and maintain a
|
|
|
|
partially sorted arrangement of data that keeps the smallest element
|
|
|
|
at position ``0``. These functions are suitable for implementing
|
|
|
|
priority queues which are commonly used for task scheduling.
|