cpython/Doc/library/collections.rst

543 lines
18 KiB
ReStructuredText
Raw Normal View History

2007-08-15 11:28:01 -03:00
:mod:`collections` --- High-performance container datatypes
===========================================================
.. module:: collections
:synopsis: High-performance datatypes
.. moduleauthor:: Raymond Hettinger <python@rcn.com>
.. sectionauthor:: Raymond Hettinger <python@rcn.com>
.. versionadded:: 2.4
This module implements high-performance container datatypes. Currently,
there are two datatypes, :class:`deque` and :class:`defaultdict`, and
one datatype factory function, :func:`namedtuple`. Python already
2007-08-15 11:28:01 -03:00
includes built-in containers, :class:`dict`, :class:`list`,
:class:`set`, and :class:`tuple`. In addition, the optional :mod:`bsddb`
module has a :meth:`bsddb.btopen` method that can be used to create in-memory
or file based ordered dictionaries with string keys.
Future editions of the standard library may include balanced trees and
ordered dictionaries.
.. versionchanged:: 2.5
Added :class:`defaultdict`.
.. versionchanged:: 2.6
Added :func:`namedtuple`.
2007-08-15 11:28:01 -03:00
.. _deque-objects:
:class:`deque` objects
----------------------
.. class:: deque([iterable[, maxlen]])
2007-08-15 11:28:01 -03:00
Returns a new deque object initialized left-to-right (using :meth:`append`) with
data from *iterable*. If *iterable* is not specified, the new deque is empty.
Deques are a generalization of stacks and queues (the name is pronounced "deck"
and is short for "double-ended queue"). Deques support thread-safe, memory
efficient appends and pops from either side of the deque with approximately the
same O(1) performance in either direction.
Though :class:`list` objects support similar operations, they are optimized for
fast fixed-length operations and incur O(n) memory movement costs for
``pop(0)`` and ``insert(0, v)`` operations which change both the size and
position of the underlying data representation.
.. versionadded:: 2.4
If *maxlen* is not specified or is *None*, deques may grow to an
arbitrary length. Otherwise, the deque is bounded to the specified maximum
length. Once a bounded length deque is full, when new items are added, a
corresponding number of items are discarded from the opposite end. Bounded
length deques provide functionality similar to the ``tail`` filter in
Unix. They are also useful for tracking transactions and other pools of data
where only the most recent activity is of interest.
.. versionchanged:: 2.6
2007-12-29 06:57:00 -04:00
Added *maxlen* parameter.
2007-08-15 11:28:01 -03:00
Deque objects support the following methods:
.. method:: deque.append(x)
Add *x* to the right side of the deque.
.. method:: deque.appendleft(x)
Add *x* to the left side of the deque.
.. method:: deque.clear()
Remove all elements from the deque leaving it with length 0.
.. method:: deque.extend(iterable)
Extend the right side of the deque by appending elements from the iterable
argument.
.. method:: deque.extendleft(iterable)
Extend the left side of the deque by appending elements from *iterable*. Note,
the series of left appends results in reversing the order of elements in the
iterable argument.
.. method:: deque.pop()
Remove and return an element from the right side of the deque. If no elements
are present, raises an :exc:`IndexError`.
.. method:: deque.popleft()
Remove and return an element from the left side of the deque. If no elements are
present, raises an :exc:`IndexError`.
.. method:: deque.remove(value)
Removed the first occurrence of *value*. If not found, raises a
:exc:`ValueError`.
.. versionadded:: 2.5
.. method:: deque.rotate(n)
Rotate the deque *n* steps to the right. If *n* is negative, rotate to the
left. Rotating one step to the right is equivalent to:
``d.appendleft(d.pop())``.
In addition to the above, deques support iteration, pickling, ``len(d)``,
``reversed(d)``, ``copy.copy(d)``, ``copy.deepcopy(d)``, membership testing with
the :keyword:`in` operator, and subscript references such as ``d[-1]``.
Example::
>>> from collections import deque
>>> d = deque('ghi') # make a new deque with three items
>>> for elem in d: # iterate over the deque's elements
... print elem.upper()
G
H
I
>>> d.append('j') # add a new entry to the right side
>>> d.appendleft('f') # add a new entry to the left side
>>> d # show the representation of the deque
deque(['f', 'g', 'h', 'i', 'j'])
>>> d.pop() # return and remove the rightmost item
'j'
>>> d.popleft() # return and remove the leftmost item
'f'
>>> list(d) # list the contents of the deque
['g', 'h', 'i']
>>> d[0] # peek at leftmost item
'g'
>>> d[-1] # peek at rightmost item
'i'
>>> list(reversed(d)) # list the contents of a deque in reverse
['i', 'h', 'g']
>>> 'h' in d # search the deque
True
>>> d.extend('jkl') # add multiple elements at once
>>> d
deque(['g', 'h', 'i', 'j', 'k', 'l'])
>>> d.rotate(1) # right rotation
>>> d
deque(['l', 'g', 'h', 'i', 'j', 'k'])
>>> d.rotate(-1) # left rotation
>>> d
deque(['g', 'h', 'i', 'j', 'k', 'l'])
>>> deque(reversed(d)) # make a new deque in reverse order
deque(['l', 'k', 'j', 'i', 'h', 'g'])
>>> d.clear() # empty the deque
>>> d.pop() # cannot pop from an empty deque
Traceback (most recent call last):
File "<pyshell#6>", line 1, in -toplevel-
d.pop()
IndexError: pop from an empty deque
>>> d.extendleft('abc') # extendleft() reverses the input order
>>> d
deque(['c', 'b', 'a'])
.. _deque-recipes:
:class:`deque` Recipes
^^^^^^^^^^^^^^^^^^^^^^
2007-08-15 11:28:01 -03:00
This section shows various approaches to working with deques.
The :meth:`rotate` method provides a way to implement :class:`deque` slicing and
deletion. For example, a pure python implementation of ``del d[n]`` relies on
the :meth:`rotate` method to position elements to be popped::
def delete_nth(d, n):
d.rotate(-n)
d.popleft()
d.rotate(n)
To implement :class:`deque` slicing, use a similar approach applying
:meth:`rotate` to bring a target element to the left side of the deque. Remove
old entries with :meth:`popleft`, add new entries with :meth:`extend`, and then
reverse the rotation.
With minor variations on that approach, it is easy to implement Forth style
stack manipulations such as ``dup``, ``drop``, ``swap``, ``over``, ``pick``,
``rot``, and ``roll``.
Multi-pass data reduction algorithms can be succinctly expressed and efficiently
coded by extracting elements with multiple calls to :meth:`popleft`, applying
a reduction function, and calling :meth:`append` to add the result back to the
deque.
2007-08-15 11:28:01 -03:00
For example, building a balanced binary tree of nested lists entails reducing
two adjacent nodes into one by grouping them in a list::
>>> def maketree(iterable):
... d = deque(iterable)
... while len(d) > 1:
... pair = [d.popleft(), d.popleft()]
... d.append(pair)
... return list(d)
...
>>> print maketree('abcdefgh')
[[[['a', 'b'], ['c', 'd']], [['e', 'f'], ['g', 'h']]]]
Bounded length deques provide functionality similar to the ``tail`` filter
in Unix::
2007-08-15 11:28:01 -03:00
def tail(filename, n=10):
'Return the last n lines of a file'
return deque(open(filename), n)
2007-08-15 11:28:01 -03:00
.. _defaultdict-objects:
:class:`defaultdict` objects
----------------------------
.. class:: defaultdict([default_factory[, ...]])
Returns a new dictionary-like object. :class:`defaultdict` is a subclass of the
builtin :class:`dict` class. It overrides one method and adds one writable
instance variable. The remaining functionality is the same as for the
:class:`dict` class and is not documented here.
The first argument provides the initial value for the :attr:`default_factory`
attribute; it defaults to ``None``. All remaining arguments are treated the same
as if they were passed to the :class:`dict` constructor, including keyword
arguments.
.. versionadded:: 2.5
:class:`defaultdict` objects support the following method in addition to the
standard :class:`dict` operations:
.. method:: defaultdict.__missing__(key)
If the :attr:`default_factory` attribute is ``None``, this raises an
:exc:`KeyError` exception with the *key* as argument.
If :attr:`default_factory` is not ``None``, it is called without arguments to
provide a default value for the given *key*, this value is inserted in the
dictionary for the *key*, and returned.
If calling :attr:`default_factory` raises an exception this exception is
propagated unchanged.
This method is called by the :meth:`__getitem__` method of the :class:`dict`
class when the requested key is not found; whatever it returns or raises is then
returned or raised by :meth:`__getitem__`.
:class:`defaultdict` objects support the following instance variable:
.. attribute:: defaultdict.default_factory
This attribute is used by the :meth:`__missing__` method; it is initialized from
the first argument to the constructor, if present, or to ``None``, if absent.
.. _defaultdict-examples:
:class:`defaultdict` Examples
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Using :class:`list` as the :attr:`default_factory`, it is easy to group a
sequence of key-value pairs into a dictionary of lists::
>>> s = [('yellow', 1), ('blue', 2), ('yellow', 3), ('blue', 4), ('red', 1)]
>>> d = defaultdict(list)
>>> for k, v in s:
... d[k].append(v)
...
>>> d.items()
[('blue', [2, 4]), ('red', [1]), ('yellow', [1, 3])]
When each key is encountered for the first time, it is not already in the
mapping; so an entry is automatically created using the :attr:`default_factory`
function which returns an empty :class:`list`. The :meth:`list.append`
operation then attaches the value to the new list. When keys are encountered
again, the look-up proceeds normally (returning the list for that key) and the
:meth:`list.append` operation adds another value to the list. This technique is
simpler and faster than an equivalent technique using :meth:`dict.setdefault`::
>>> d = {}
>>> for k, v in s:
... d.setdefault(k, []).append(v)
...
>>> d.items()
[('blue', [2, 4]), ('red', [1]), ('yellow', [1, 3])]
Setting the :attr:`default_factory` to :class:`int` makes the
:class:`defaultdict` useful for counting (like a bag or multiset in other
languages)::
>>> s = 'mississippi'
>>> d = defaultdict(int)
>>> for k in s:
... d[k] += 1
...
>>> d.items()
[('i', 4), ('p', 2), ('s', 4), ('m', 1)]
When a letter is first encountered, it is missing from the mapping, so the
:attr:`default_factory` function calls :func:`int` to supply a default count of
zero. The increment operation then builds up the count for each letter.
The function :func:`int` which always returns zero is just a special case of
constant functions. A faster and more flexible way to create constant functions
is to use :func:`itertools.repeat` which can supply any constant value (not just
zero)::
>>> def constant_factory(value):
... return itertools.repeat(value).next
>>> d = defaultdict(constant_factory('<missing>'))
>>> d.update(name='John', action='ran')
>>> '%(name)s %(action)s to %(object)s' % d
'John ran to <missing>'
Setting the :attr:`default_factory` to :class:`set` makes the
:class:`defaultdict` useful for building a dictionary of sets::
>>> s = [('red', 1), ('blue', 2), ('red', 3), ('blue', 4), ('red', 1), ('blue', 4)]
>>> d = defaultdict(set)
>>> for k, v in s:
... d[k].add(v)
...
>>> d.items()
[('blue', set([2, 4])), ('red', set([1, 3]))]
.. _named-tuple-factory:
:func:`namedtuple` Factory Function for Tuples with Named Fields
2007-10-08 18:26:58 -03:00
-----------------------------------------------------------------
2007-08-15 11:28:01 -03:00
2007-09-18 19:18:02 -03:00
Named tuples assign meaning to each position in a tuple and allow for more readable,
self-documenting code. They can be used wherever regular tuples are used, and
they add the ability to access fields by name instead of position index.
2007-08-15 11:28:01 -03:00
.. function:: namedtuple(typename, fieldnames, [verbose])
2007-08-15 11:28:01 -03:00
Returns a new tuple subclass named *typename*. The new subclass is used to
create tuple-like objects that have fields accessable by attribute lookup as
well as being indexable and iterable. Instances of the subclass also have a
helpful docstring (with typename and fieldnames) and a helpful :meth:`__repr__`
method which lists the tuple contents in a ``name=value`` format.
2007-10-08 18:26:58 -03:00
The *fieldnames* are a single string with each fieldname separated by whitespace
and/or commas (for example 'x y' or 'x, y'). Alternatively, the *fieldnames*
2007-10-16 18:28:32 -03:00
can be specified as a list of strings (such as ['x', 'y']).
Any valid Python identifier may be used for a fieldname except for names
2007-12-13 22:49:47 -04:00
starting with an underscore. Valid identifiers consist of letters, digits,
and underscores but do not start with a digit or underscore and cannot be
2007-10-16 18:28:32 -03:00
a :mod:`keyword` such as *class*, *for*, *return*, *global*, *pass*, *print*,
or *raise*.
2007-09-18 19:18:02 -03:00
2007-09-20 00:03:43 -03:00
If *verbose* is true, will print the class definition.
2007-09-18 19:18:02 -03:00
2007-10-08 18:26:58 -03:00
Named tuple instances do not have per-instance dictionaries, so they are
2007-09-20 00:03:43 -03:00
lightweight and require no more memory than regular tuples.
2007-09-18 19:18:02 -03:00
2007-08-15 11:28:01 -03:00
.. versionadded:: 2.6
2007-09-18 19:18:02 -03:00
Example::
>>> Point = namedtuple('Point', 'x y', verbose=True)
2007-09-18 19:18:02 -03:00
class Point(tuple):
'Point(x, y)'
2007-12-14 14:08:20 -04:00
2007-09-18 19:18:02 -03:00
__slots__ = ()
2007-12-14 14:08:20 -04:00
_fields = ('x', 'y')
2007-09-18 19:18:02 -03:00
def __new__(cls, x, y):
return tuple.__new__(cls, (x, y))
2007-12-14 14:08:20 -04:00
@classmethod
def _make(cls, iterable):
'Make a new Point object from a sequence or iterable'
result = tuple.__new__(cls, iterable)
if len(result) != 2:
raise TypeError('Expected 2 arguments, got %d' % len(result))
return result
2007-09-18 19:18:02 -03:00
def __repr__(self):
return 'Point(x=%r, y=%r)' % self
2007-12-14 14:08:20 -04:00
def _asdict(t):
2007-12-14 14:08:20 -04:00
'Return a new dict which maps field names to their values'
return {'x': t[0], 'y': t[1]}
2007-12-14 14:08:20 -04:00
2007-12-13 22:49:47 -04:00
def _replace(self, **kwds):
'Return a new Point object replacing specified fields with new values'
result = self._make(map(kwds.pop, ('x', 'y'), self))
if kwds:
raise ValueError('Got unexpected field names: %r' % kwds.keys())
return result
2007-09-18 19:18:02 -03:00
x = property(itemgetter(0))
y = property(itemgetter(1))
>>> p = Point(11, y=22) # instantiate with positional or keyword arguments
>>> p[0] + p[1] # indexable like the plain tuple (11, 22)
2007-09-18 19:18:02 -03:00
33
>>> x, y = p # unpack like a regular tuple
>>> x, y
(11, 22)
>>> p.x + p.y # fields also accessable by name
33
>>> p # readable __repr__ with a name=value style
Point(x=11, y=22)
Named tuples are especially useful for assigning field names to result tuples returned
by the :mod:`csv` or :mod:`sqlite3` modules::
EmployeeRecord = namedtuple('EmployeeRecord', 'name, age, title, department, paygrade')
2007-10-08 18:26:58 -03:00
2007-09-18 19:18:02 -03:00
import csv
for emp in map(EmployeeRecord._make, csv.reader(open("employees.csv", "rb"))):
2007-09-18 19:18:02 -03:00
print emp.name, emp.title
2007-10-08 18:26:58 -03:00
import sqlite3
conn = sqlite3.connect('/companydata')
cursor = conn.cursor()
cursor.execute('SELECT name, age, title, department, paygrade FROM employees')
for emp in map(EmployeeRecord._make, cursor.fetchall()):
2007-10-08 18:26:58 -03:00
print emp.name, emp.title
In addition to the methods inherited from tuples, named tuples support
three additional methods and one attribute.
2007-09-18 19:18:02 -03:00
.. method:: namedtuple._make(iterable)
Class method that makes a new instance from an existing sequence or iterable.
::
>>> t = [11, 22]
>>> Point._make(t)
Point(x=11, y=22)
2007-12-13 22:49:47 -04:00
.. method:: somenamedtuple._asdict()
Return a new dict which maps field names to their corresponding values:
::
2007-12-13 22:49:47 -04:00
>>> p._asdict()
{'x': 11, 'y': 22}
2007-12-13 22:49:47 -04:00
.. method:: somenamedtuple._replace(kwargs)
Return a new instance of the named tuple replacing specified fields with new values:
2007-09-20 00:03:43 -03:00
::
2007-09-18 19:18:02 -03:00
>>> p = Point(x=11, y=22)
2007-12-13 22:49:47 -04:00
>>> p._replace(x=33)
Point(x=33, y=22)
2007-11-14 23:16:09 -04:00
>>> for partnum, record in inventory.items():
2007-12-13 22:49:47 -04:00
... inventory[partnum] = record._replace(price=newprices[partnum], updated=time.now())
2007-12-13 22:49:47 -04:00
.. attribute:: somenamedtuple._fields
Tuple of strings listing the field names. This is useful for introspection
and for creating new named tuple types from existing named tuples.
2007-09-20 00:03:43 -03:00
::
2007-09-18 19:18:02 -03:00
2007-12-13 22:49:47 -04:00
>>> p._fields # view the field names
2007-09-18 19:18:02 -03:00
('x', 'y')
>>> Color = namedtuple('Color', 'red green blue')
2007-12-13 22:49:47 -04:00
>>> Pixel = namedtuple('Pixel', Point._fields + Color._fields)
2007-09-18 19:18:02 -03:00
>>> Pixel(11, 22, 128, 255, 0)
Pixel(x=11, y=22, red=128, green=255, blue=0)'
2007-12-14 17:51:50 -04:00
To retrieve a field whose name is stored in a string, use the :func:`getattr`
function:
::
>>> getattr(p, 'x')
11
When casting a dictionary to a named tuple, use the double-star-operator [#]_::
>>> d = {'x': 11, 'y': 22}
>>> Point(**d)
Point(x=11, y=22)
Since a named tuple is a regular Python class, it is easy to add or change
functionality with a subclass. Here is how to add a calculated field and
a custom fixed-width print format:
::
>>> class Point(namedtuple('Point', 'x y')):
@property
def hypot(self):
return (self.x ** 2 + self.y ** 2) ** 0.5
def __repr__(self):
return 'Point(x=%.3f, y=%.3f, hypot=%.3f)' % (self.x, self.y, self.hypot)
>>> print Point(3, 4)
Point(x=3.000, y=4.000, hypot=5.000)
>>> Point(2, 5)
Point(x=2.000, y=5.000, hypot=5.385)
Default values can be implemented by starting with a prototype instance
2007-12-13 22:49:47 -04:00
and customizing it with :meth:`_replace`:
::
>>> Account = namedtuple('Account', 'owner balance transaction_count')
>>> model_account = Account('<owner name>', 0.0, 0)
2007-12-13 22:49:47 -04:00
>>> johns_account = model_account._replace(owner='John')
2007-08-30 12:03:03 -03:00
.. rubric:: Footnotes
.. [#] For information on the double-star-operator see
2007-08-30 12:03:03 -03:00
:ref:`tut-unpacking-arguments` and :ref:`calls`.