ℹ️ Skipped - page is already crawled
| Filter | Status | Condition | Details |
|---|---|---|---|
| HTTP status | PASS | download_http_code = 200 | HTTP 200 |
| Age cutoff | PASS | download_stamp > now() - 6 MONTH | 0.4 months ago |
| History drop | PASS | isNull(history_drop_reason) | No drop reason |
| Spam/ban | PASS | fh_dont_index != 1 AND ml_spam_score = 0 | ml_spam_score=0 |
| Canonical | PASS | meta_canonical IS NULL OR = '' OR = src_unparsed | Not set |
| Property | Value | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| URL | https://docs.python.org/3/library/collections.html | |||||||||
| Last Crawled | 2026-04-10 03:30:21 (12 days ago) | |||||||||
| First Indexed | 2014-04-05 01:30:14 (12 years ago) | |||||||||
| HTTP Status Code | 200 | |||||||||
| Content | ||||||||||
| Meta Title | collections — Container datatypes — Python 3.14.4 documentation | |||||||||
| Meta Description | Source code: Lib/collections/__init__.py This module implements specialized container datatypes providing alternatives to Python’s general purpose built-in containers, dict, list, set, and tuple.,,... | |||||||||
| Meta Canonical | null | |||||||||
| Boilerpipe Text | Source code:
Lib/collections/__init__.py
This module implements specialized container datatypes providing alternatives to
Python’s general purpose built-in containers,
dict
,
list
,
set
, and
tuple
.
namedtuple()
factory function for creating tuple subclasses with named fields
deque
list-like container with fast appends and pops on either end
ChainMap
dict-like class for creating a single view of multiple mappings
Counter
dict subclass for counting
hashable
objects
OrderedDict
dict subclass that remembers the order entries were added
defaultdict
dict subclass that calls a factory function to supply missing values
UserDict
wrapper around dictionary objects for easier dict subclassing
UserList
wrapper around list objects for easier list subclassing
UserString
wrapper around string objects for easier string subclassing
ChainMap
objects
¶
Added in version 3.3.
A
ChainMap
class is provided for quickly linking a number of mappings
so they can be treated as a single unit. It is often much faster than creating
a new dictionary and running multiple
update()
calls.
The class can be used to simulate nested scopes and is useful in templating.
class
collections.
ChainMap
(
*
maps
)
¶
A
ChainMap
groups multiple dicts or other mappings together to
create a single, updateable view. If no
maps
are specified, a single empty
dictionary is provided so that a new chain always has at least one mapping.
The underlying mappings are stored in a list. That list is public and can
be accessed or updated using the
maps
attribute. There is no other state.
Lookups search the underlying mappings successively until a key is found. In
contrast, writes, updates, and deletions only operate on the first mapping.
A
ChainMap
incorporates the underlying mappings by reference. So, if
one of the underlying mappings gets updated, those changes will be reflected
in
ChainMap
.
All of the usual dictionary methods are supported. In addition, there is a
maps
attribute, a method for creating new subcontexts, and a property for
accessing all but the first mapping:
maps
¶
A user updateable list of mappings. The list is ordered from
first-searched to last-searched. It is the only stored state and can
be modified to change which mappings are searched. The list should
always contain at least one mapping.
new_child
(
m
=
None
,
**
kwargs
)
¶
Returns a new
ChainMap
containing a new map followed by
all of the maps in the current instance. If
m
is specified,
it becomes the new map at the front of the list of mappings; if not
specified, an empty dict is used, so that a call to
d.new_child()
is equivalent to:
ChainMap({},
*d.maps)
. If any keyword arguments
are specified, they update passed map or new empty dict. This method
is used for creating subcontexts that can be updated without altering
values in any of the parent mappings.
Changed in version 3.4:
The optional
m
parameter was added.
Changed in version 3.10:
Keyword arguments support was added.
parents
¶
Property returning a new
ChainMap
containing all of the maps in
the current instance except the first one. This is useful for skipping
the first map in the search. Use cases are similar to those for the
nonlocal
keyword used in
nested scopes
. The use cases also parallel those for the built-in
super()
function. A reference to
d.parents
is equivalent to:
ChainMap(*d.maps[1:])
.
Note, the iteration order of a
ChainMap
is determined by
scanning the mappings last to first:
>>>
baseline
=
{
'music'
:
'bach'
,
'art'
:
'rembrandt'
}
>>>
adjustments
=
{
'art'
:
'van gogh'
,
'opera'
:
'carmen'
}
>>>
list
(
ChainMap
(
adjustments
,
baseline
))
['music', 'art', 'opera']
This gives the same ordering as a series of
dict.update()
calls
starting with the last mapping:
>>>
combined
=
baseline
.
copy
()
>>>
combined
.
update
(
adjustments
)
>>>
list
(
combined
)
['music', 'art', 'opera']
Changed in version 3.9:
Added support for
|
and
|=
operators, specified in
PEP 584
.
See also
The
MultiContext class
in the Enthought
CodeTools package
has options to support
writing to any mapping in the chain.
Django’s
Context class
for templating is a read-only chain of mappings. It also features
pushing and popping of contexts similar to the
new_child()
method and the
parents
property.
The
Nested Contexts recipe
has options to control
whether writes and other mutations apply only to the first mapping or to
any mapping in the chain.
A
greatly simplified read-only version of Chainmap
.
ChainMap
Examples and Recipes
¶
This section shows various approaches to working with chained maps.
Example of simulating Python’s internal lookup chain:
import
builtins
pylookup
=
ChainMap
(
locals
(),
globals
(),
vars
(
builtins
))
Example of letting user specified command-line arguments take precedence over
environment variables which in turn take precedence over default values:
import
os
,
argparse
defaults
=
{
'color'
:
'red'
,
'user'
:
'guest'
}
parser
=
argparse
.
ArgumentParser
()
parser
.
add_argument
(
'-u'
,
'--user'
)
parser
.
add_argument
(
'-c'
,
'--color'
)
namespace
=
parser
.
parse_args
()
command_line_args
=
{
k
:
v
for
k
,
v
in
vars
(
namespace
)
.
items
()
if
v
is
not
None
}
combined
=
ChainMap
(
command_line_args
,
os
.
environ
,
defaults
)
print
(
combined
[
'color'
])
print
(
combined
[
'user'
])
Example patterns for using the
ChainMap
class to simulate nested
contexts:
c
=
ChainMap
()
# Create root context
d
=
c
.
new_child
()
# Create nested child context
e
=
c
.
new_child
()
# Child of c, independent from d
e
.
maps
[
0
]
# Current context dictionary -- like Python's locals()
e
.
maps
[
-
1
]
# Root context -- like Python's globals()
e
.
parents
# Enclosing context chain -- like Python's nonlocals
d
[
'x'
]
=
1
# Set value in current context
d
[
'x'
]
# Get first key in the chain of contexts
del
d
[
'x'
]
# Delete from current context
list
(
d
)
# All nested values
k
in
d
# Check all nested values
len
(
d
)
# Number of nested values
d
.
items
()
# All nested items
dict
(
d
)
# Flatten into a regular dictionary
The
ChainMap
class only makes updates (writes and deletions) to the
first mapping in the chain while lookups will search the full chain. However,
if deep writes and deletions are desired, it is easy to make a subclass that
updates keys found deeper in the chain:
class
DeepChainMap
(
ChainMap
):
'Variant of ChainMap that allows direct updates to inner scopes'
def
__setitem__
(
self
,
key
,
value
):
for
mapping
in
self
.
maps
:
if
key
in
mapping
:
mapping
[
key
]
=
value
return
self
.
maps
[
0
][
key
]
=
value
def
__delitem__
(
self
,
key
):
for
mapping
in
self
.
maps
:
if
key
in
mapping
:
del
mapping
[
key
]
return
raise
KeyError
(
key
)
>>>
d
=
DeepChainMap
({
'zebra'
:
'black'
},
{
'elephant'
:
'blue'
},
{
'lion'
:
'yellow'
})
>>>
d
[
'lion'
]
=
'orange'
# update an existing key two levels down
>>>
d
[
'snake'
]
=
'red'
# new keys get added to the topmost dict
>>>
del
d
[
'elephant'
]
# remove an existing key one level down
>>>
d
# display result
DeepChainMap
({
'zebra'
:
'black'
,
'snake'
:
'red'
},
{},
{
'lion'
:
'orange'
})
Counter
objects
¶
A counter tool is provided to support convenient and rapid tallies.
For example:
>>>
# Tally occurrences of words in a list
>>>
cnt
=
Counter
()
>>>
for
word
in
[
'red'
,
'blue'
,
'red'
,
'green'
,
'blue'
,
'blue'
]:
...
cnt
[
word
]
+=
1
...
>>>
cnt
Counter({'blue': 3, 'red': 2, 'green': 1})
>>>
# Find the ten most common words in Hamlet
>>>
import
re
>>>
words
=
re
.
findall
(
r
'\w+'
,
open
(
'hamlet.txt'
)
.
read
()
.
lower
())
>>>
Counter
(
words
)
.
most_common
(
10
)
[('the', 1143), ('and', 966), ('to', 762), ('of', 669), ('i', 631),
('you', 554), ('a', 546), ('my', 514), ('hamlet', 471), ('in', 451)]
class
collections.
Counter
(
**
kwargs
)
¶
class
collections.
Counter
(
iterable
,
/
,
**
kwargs
)
class
collections.
Counter
(
mapping
,
/
,
**
kwargs
)
A
Counter
is a
dict
subclass for counting
hashable
objects.
It is a collection where elements are stored as dictionary keys
and their counts are stored as dictionary values. Counts are allowed to be
any integer value including zero or negative counts. The
Counter
class is similar to bags or multisets in other languages.
Elements are counted from an
iterable
or initialized from another
mapping
(or counter):
>>>
c
=
Counter
()
# a new, empty counter
>>>
c
=
Counter
(
'gallahad'
)
# a new counter from an iterable
>>>
c
=
Counter
({
'red'
:
4
,
'blue'
:
2
})
# a new counter from a mapping
>>>
c
=
Counter
(
cats
=
4
,
dogs
=
8
)
# a new counter from keyword args
Counter objects have a dictionary interface except that they return a zero
count for missing items instead of raising a
KeyError
:
>>>
c
=
Counter
([
'eggs'
,
'ham'
])
>>>
c
[
'bacon'
]
# count of a missing element is zero
0
Setting a count to zero does not remove an element from a counter.
Use
del
to remove it entirely:
>>>
c
[
'sausage'
]
=
0
# counter entry with a zero count
>>>
del
c
[
'sausage'
]
# del actually removes the entry
Added in version 3.1.
Changed in version 3.7:
As a
dict
subclass,
Counter
inherited the capability to remember insertion order. Math operations
on
Counter
objects also preserve order. Results are ordered
according to when an element is first encountered in the left operand
and then by the order encountered in the right operand.
Counter objects support additional methods beyond those available for all
dictionaries:
elements
(
)
¶
Return an iterator over elements repeating each as many times as its
count. Elements are returned in the order first encountered. If an
element’s count is less than one,
elements()
will ignore it.
>>>
c
=
Counter
(
a
=
4
,
b
=
2
,
c
=
0
,
d
=-
2
)
>>>
sorted
(
c
.
elements
())
['a', 'a', 'a', 'a', 'b', 'b']
most_common
(
n
=
None
)
¶
Return a list of the
n
most common elements and their counts from the
most common to the least. If
n
is omitted or
None
,
most_common()
returns
all
elements in the counter.
Elements with equal counts are ordered in the order first encountered:
>>>
Counter
(
'abracadabra'
)
.
most_common
(
3
)
[('a', 5), ('b', 2), ('r', 2)]
subtract
(
**
kwargs
)
¶
subtract
(
iterable
,
/
,
**
kwargs
)
subtract
(
mapping
,
/
,
**
kwargs
)
Elements are subtracted from an
iterable
or from another
mapping
(or counter). Like
dict.update()
but subtracts counts instead
of replacing them. Both inputs and outputs may be zero or negative.
>>>
c
=
Counter
(
a
=
4
,
b
=
2
,
c
=
0
,
d
=-
2
)
>>>
d
=
Counter
(
a
=
1
,
b
=
2
,
c
=
3
,
d
=
4
)
>>>
c
.
subtract
(
d
)
>>>
c
Counter({'a': 3, 'b': 0, 'c': -3, 'd': -6})
Added in version 3.2.
total
(
)
¶
Compute the sum of the counts.
>>>
c
=
Counter
(
a
=
10
,
b
=
5
,
c
=
0
)
>>>
c
.
total
()
15
Added in version 3.10.
The usual dictionary methods are available for
Counter
objects
except for two which work differently for counters.
fromkeys
(
iterable
)
¶
This class method is not implemented for
Counter
objects.
update
(
**
kwargs
)
¶
update
(
iterable
,
/
,
**
kwargs
)
update
(
mapping
,
/
,
**
kwargs
)
Elements are counted from an
iterable
or added-in from another
mapping
(or counter). Like
dict.update()
but adds counts
instead of replacing them. Also, the
iterable
is expected to be a
sequence of elements, not a sequence of
(key,
value)
pairs.
Counters support rich comparison operators for equality, subset, and
superset relationships:
==
,
!=
,
<
,
<=
,
>
,
>=
.
All of those tests treat missing elements as having zero counts so that
Counter(a=1)
==
Counter(a=1,
b=0)
returns true.
Changed in version 3.10:
Rich comparison operations were added.
Changed in version 3.10:
In equality tests, missing elements are treated as having zero counts.
Formerly,
Counter(a=3)
and
Counter(a=3,
b=0)
were considered
distinct.
Common patterns for working with
Counter
objects:
c
.
total
()
# total of all counts
c
.
clear
()
# reset all counts
list
(
c
)
# list unique elements
set
(
c
)
# convert to a set
dict
(
c
)
# convert to a regular dictionary
c
.
items
()
# access the (elem, cnt) pairs
Counter
(
dict
(
list_of_pairs
))
# convert from a list of (elem, cnt) pairs
c
.
most_common
()[:
-
n
-
1
:
-
1
]
# n least common elements
+
c
# remove zero and negative counts
Several mathematical operations are provided for combining
Counter
objects to produce multisets (counters that have counts greater than zero).
Addition and subtraction combine counters by adding or subtracting the counts
of corresponding elements. Intersection and union return the minimum and
maximum of corresponding counts. Equality and inclusion compare
corresponding counts. Each operation can accept inputs with signed
counts, but the output will exclude results with counts of zero or less.
>>>
c
=
Counter
(
a
=
3
,
b
=
1
)
>>>
d
=
Counter
(
a
=
1
,
b
=
2
)
>>>
c
+
d
# add two counters together: c[x] + d[x]
Counter({'a': 4, 'b': 3})
>>>
c
-
d
# subtract (keeping only positive counts)
Counter({'a': 2})
>>>
c
&
d
# intersection: min(c[x], d[x])
Counter({'a': 1, 'b': 1})
>>>
c
|
d
# union: max(c[x], d[x])
Counter({'a': 3, 'b': 2})
>>>
c
==
d
# equality: c[x] == d[x]
False
>>>
c
<=
d
# inclusion: c[x] <= d[x]
False
Unary addition and subtraction are shortcuts for adding an empty counter
or subtracting from an empty counter.
>>>
c
=
Counter
(
a
=
2
,
b
=-
4
)
>>>
+
c
Counter({'a': 2})
>>>
-
c
Counter({'b': 4})
Added in version 3.3:
Added support for unary plus, unary minus, and in-place multiset operations.
Note
Counters were primarily designed to work with positive integers to represent
running counts; however, care was taken to not unnecessarily preclude use
cases needing other types or negative values. To help with those use cases,
this section documents the minimum range and type restrictions.
The
Counter
class itself is a dictionary subclass with no
restrictions on its keys and values. The values are intended to be numbers
representing counts, but you
could
store anything in the value field.
The
most_common()
method requires only that the values be orderable.
For in-place operations such as
c[key]
+=
1
, the value type need only
support addition and subtraction. So fractions, floats, and decimals would
work and negative values are supported. The same is also true for
update()
and
subtract()
which allow negative and zero values
for both inputs and outputs.
The multiset methods are designed only for use cases with positive values.
The inputs may be negative or zero, but only outputs with positive values
are created. There are no type restrictions, but the value type needs to
support addition, subtraction, and comparison.
The
elements()
method requires integer counts. It ignores zero and
negative counts.
See also
Bag class
in Smalltalk.
Wikipedia entry for
Multisets
.
C++ multisets
tutorial with examples.
For mathematical operations on multisets and their use cases, see
Knuth, Donald. The Art of Computer Programming Volume II,
Section 4.6.3, Exercise 19
.
To enumerate all distinct multisets of a given size over a given set of
elements, see
itertools.combinations_with_replacement()
:
map
(
Counter
,
combinations_with_replacement
(
'ABC'
,
2
))
# --> AA AB AC BB BC CC
deque
objects
¶
class
collections.
deque
(
[
iterable
[
,
maxlen
]
]
)
¶
Returns a new deque object initialized left-to-right (using
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
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.
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.
Deque objects support the following methods:
append
(
item
,
/
)
¶
Add
item
to the right side of the deque.
appendleft
(
item
,
/
)
¶
Add
item
to the left side of the deque.
clear
(
)
¶
Remove all elements from the deque leaving it with length 0.
copy
(
)
¶
Create a shallow copy of the deque.
Added in version 3.5.
count
(
value
,
/
)
¶
Count the number of deque elements equal to
value
.
Added in version 3.2.
extend
(
iterable
,
/
)
¶
Extend the right side of the deque by appending elements from the iterable
argument.
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.
index
(
value
[
,
start
[
,
stop
]
]
)
¶
Return the position of
value
in the deque (at or after index
start
and before index
stop
). Returns the first match or raises
ValueError
if not found.
Added in version 3.5.
insert
(
index
,
value
,
/
)
¶
Insert
value
into the deque at position
index
.
If the insertion would cause a bounded deque to grow beyond
maxlen
,
an
IndexError
is raised.
Added in version 3.5.
pop
(
)
¶
Remove and return an element from the right side of the deque. If no
elements are present, raises an
IndexError
.
popleft
(
)
¶
Remove and return an element from the left side of the deque. If no
elements are present, raises an
IndexError
.
remove
(
value
,
/
)
¶
Remove the first occurrence of
value
. If not found, raises a
ValueError
.
reverse
(
)
¶
Reverse the elements of the deque in-place and then return
None
.
Added in version 3.2.
rotate
(
n
=
1
,
/
)
¶
Rotate the deque
n
steps to the right. If
n
is negative, rotate
to the left.
When the deque is not empty, rotating one step to the right is equivalent
to
d.appendleft(d.pop())
, and rotating one step to the left is
equivalent to
d.append(d.popleft())
.
Deque objects also provide one read-only attribute:
maxlen
¶
Maximum size of a deque or
None
if unbounded.
Added in version 3.1.
In addition to the above, deques support iteration, pickling,
len(d)
,
reversed(d)
,
copy.copy(d)
,
copy.deepcopy(d)
, membership testing with
the
in
operator, and subscript references such as
d[0]
to access
the first element. Indexed access is
O
(1) at both ends but slows to
O
(
n
) in
the middle. For fast random access, use lists instead.
Starting in version 3.5, deques support
__add__()
,
__mul__()
,
and
__imul__()
.
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
¶
This section shows various approaches to working with deques.
Bounded length deques provide functionality similar to the
tail
filter
in Unix:
def
tail
(
filename
,
n
=
10
):
'Return the last n lines of a file'
with
open
(
filename
)
as
f
:
return
deque
(
f
,
n
)
Another approach to using deques is to maintain a sequence of recently
added elements by appending to the right and popping to the left:
def
moving_average
(
iterable
,
n
=
3
):
# moving_average([40, 30, 50, 46, 39, 44]) --> 40.0 42.0 45.0 43.0
# https://en.wikipedia.org/wiki/Moving_average
it
=
iter
(
iterable
)
d
=
deque
(
itertools
.
islice
(
it
,
n
-
1
))
d
.
appendleft
(
0
)
s
=
sum
(
d
)
for
elem
in
it
:
s
+=
elem
-
d
.
popleft
()
d
.
append
(
elem
)
yield
s
/
n
A
round-robin scheduler
can be implemented with
input iterators stored in a
deque
. Values are yielded from the active
iterator in position zero. If that iterator is exhausted, it can be removed
with
popleft()
; otherwise, it can be cycled back to the end with
the
rotate()
method:
def
roundrobin
(
*
iterables
):
"roundrobin('ABC', 'D', 'EF') --> A D E B F C"
iterators
=
deque
(
map
(
iter
,
iterables
))
while
iterators
:
try
:
while
True
:
yield
next
(
iterators
[
0
])
iterators
.
rotate
(
-
1
)
except
StopIteration
:
# Remove an exhausted iterator.
iterators
.
popleft
()
The
rotate()
method provides a way to implement
deque
slicing and
deletion. For example, a pure Python implementation of
del
d[n]
relies on
the
rotate()
method to position elements to be popped:
def
delete_nth
(
d
,
n
):
d
.
rotate
(
-
n
)
d
.
popleft
()
d
.
rotate
(
n
)
To implement
deque
slicing, use a similar approach applying
rotate()
to bring a target element to the left side of the deque. Remove
old entries with
popleft()
, add new entries with
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
.
defaultdict
objects
¶
class
collections.
defaultdict
(
default_factory
=
None
,
/
,
**
kwargs
)
¶
class
collections.
defaultdict
(
default_factory
,
mapping
,
/
,
**
kwargs
)
class
collections.
defaultdict
(
default_factory
,
iterable
,
/
,
**
kwargs
)
Return a new dictionary-like object.
defaultdict
is a subclass of the
built-in
dict
class. It overrides one method and adds one writable
instance variable. The remaining functionality is the same as for the
dict
class and is not documented here.
The first argument provides the initial value for the
default_factory
attribute; it defaults to
None
. All remaining arguments are treated the same
as if they were passed to the
dict
constructor, including keyword
arguments.
defaultdict
objects support the following method in addition to the
standard
dict
operations:
__missing__
(
key
,
/
)
¶
If the
default_factory
attribute is
None
, this raises a
KeyError
exception with the
key
as argument.
If
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
default_factory
raises an exception this exception is
propagated unchanged.
This method is called by the
__getitem__()
method of the
dict
class when the requested key is not found; whatever it
returns or raises is then returned or raised by
__getitem__()
.
Note that
__missing__()
is
not
called for any operations besides
__getitem__()
. This means that
get()
will, like
normal dictionaries, return
None
as a default rather than using
default_factory
.
defaultdict
objects support the following instance variable:
default_factory
¶
This attribute is used by the
__missing__()
method;
it is initialized from the first argument to the constructor, if present,
or to
None
, if absent.
Changed in version 3.9:
Added merge (
|
) and update (
|=
) operators, specified in
PEP 584
.
defaultdict
Examples
¶
Using
list
as the
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
)
...
>>>
sorted
(
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
default_factory
function which returns an empty
list
. The
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
list.append()
operation adds another value to the list. This technique is
simpler and faster than an equivalent technique using
dict.setdefault()
:
>>>
d
=
{}
>>>
for
k
,
v
in
s
:
...
d
.
setdefault
(
k
,
[])
.
append
(
v
)
...
>>>
sorted
(
d
.
items
())
[('blue', [2, 4]), ('red', [1]), ('yellow', [1, 3])]
Setting the
default_factory
to
int
makes the
defaultdict
useful for counting (like a bag or multiset in other
languages):
>>>
s
=
'mississippi'
>>>
d
=
defaultdict
(
int
)
>>>
for
k
in
s
:
...
d
[
k
]
+=
1
...
>>>
sorted
(
d
.
items
())
[('i', 4), ('m', 1), ('p', 2), ('s', 4)]
When a letter is first encountered, it is missing from the mapping, so the
default_factory
function calls
int()
to supply a default count of
zero. The increment operation then builds up the count for each letter.
The function
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 a lambda function which can supply any constant value (not just
zero):
>>>
def
constant_factory
(
value
):
...
return
lambda
:
value
...
>>>
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
default_factory
to
set
makes the
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
)
...
>>>
sorted
(
d
.
items
())
[('blue', {2, 4}), ('red', {1, 3})]
namedtuple()
Factory Function for Tuples with Named Fields
¶
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.
collections.
namedtuple
(
typename
,
field_names
,
*
,
rename
=
False
,
defaults
=
None
,
module
=
None
)
¶
Returns a new tuple subclass named
typename
. The new subclass is used to
create tuple-like objects that have fields accessible by attribute lookup as
well as being indexable and iterable. Instances of the subclass also have a
helpful docstring (with
typename
and
field_names
) and a helpful
__repr__()
method which lists the tuple contents in a
name=value
format.
The
field_names
are a sequence of strings such as
['x',
'y']
.
Alternatively,
field_names
can be a single string with each fieldname
separated by whitespace and/or commas, for example
'x
y'
or
'x,
y'
.
Any valid Python identifier may be used for a fieldname except for names
starting with an underscore. Valid identifiers consist of letters, digits,
and underscores but do not start with a digit or underscore and cannot be
a
keyword
such as
class
,
for
,
return
,
global
,
pass
,
or
raise
.
If
rename
is true, invalid fieldnames are automatically replaced
with positional names. For example,
['abc',
'def',
'ghi',
'abc']
is
converted to
['abc',
'_1',
'ghi',
'_3']
, eliminating the keyword
def
and the duplicate fieldname
abc
.
defaults
can be
None
or an
iterable
of default values.
Since fields with a default value must come after any fields without a
default, the
defaults
are applied to the rightmost parameters. For
example, if the fieldnames are
['x',
'y',
'z']
and the defaults are
(1,
2)
, then
x
will be a required argument,
y
will default to
1
, and
z
will default to
2
.
If
module
is defined, the
__module__
attribute of the
named tuple is set to that value.
Named tuple instances do not have per-instance dictionaries, so they are
lightweight and require no more memory than regular tuples.
To support pickling, the named tuple class should be assigned to a variable
that matches
typename
.
Changed in version 3.1:
Added support for
rename
.
Changed in version 3.6:
Added the
module
parameter.
Changed in version 3.7:
Removed the
verbose
parameter and the
_source
attribute.
Changed in version 3.7:
Added the
defaults
parameter and the
_field_defaults
attribute.
>>>
# Basic example
>>>
Point
=
namedtuple
(
'Point'
,
[
'x'
,
'y'
])
>>>
p
=
Point
(
11
,
y
=
22
)
# instantiate with positional or keyword arguments
>>>
p
[
0
]
+
p
[
1
]
# indexable like the plain tuple (11, 22)
33
>>>
x
,
y
=
p
# unpack like a regular tuple
>>>
x
,
y
(11, 22)
>>>
p
.
x
+
p
.
y
# fields also accessible 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
csv
or
sqlite3
modules:
EmployeeRecord
=
namedtuple
(
'EmployeeRecord'
,
'name, age, title, department, paygrade'
)
import
csv
for
emp
in
map
(
EmployeeRecord
.
_make
,
csv
.
reader
(
open
(
"employees.csv"
,
"rb"
))):
print
(
emp
.
name
,
emp
.
title
)
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
()):
print
(
emp
.
name
,
emp
.
title
)
In addition to the methods inherited from tuples, named tuples support
three additional methods and two attributes. To prevent conflicts with
field names, the method and attribute names start with an underscore.
classmethod
somenamedtuple.
_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)
somenamedtuple.
_asdict
(
)
¶
Return a new
dict
which maps field names to their corresponding
values:
>>>
p
=
Point
(
x
=
11
,
y
=
22
)
>>>
p
.
_asdict
()
{'x': 11, 'y': 22}
Changed in version 3.1:
Returns an
OrderedDict
instead of a regular
dict
.
Changed in version 3.8:
Returns a regular
dict
instead of an
OrderedDict
.
As of Python 3.7, regular dicts are guaranteed to be ordered. If the
extra features of
OrderedDict
are required, the suggested
remediation is to cast the result to the desired type:
OrderedDict(nt._asdict())
.
somenamedtuple.
_replace
(
**
kwargs
)
¶
Return a new instance of the named tuple replacing specified fields with new
values:
>>>
p
=
Point
(
x
=
11
,
y
=
22
)
>>>
p
.
_replace
(
x
=
33
)
Point(x=33, y=22)
>>>
for
partnum
,
record
in
inventory
.
items
():
...
inventory
[
partnum
]
=
record
.
_replace
(
price
=
newprices
[
partnum
],
timestamp
=
time
.
now
())
Named tuples are also supported by generic function
copy.replace()
.
Changed in version 3.13:
Raise
TypeError
instead of
ValueError
for invalid
keyword arguments.
somenamedtuple.
_fields
¶
Tuple of strings listing the field names. Useful for introspection
and for creating new named tuple types from existing named tuples.
>>>
p
.
_fields
# view the field names
('x', 'y')
>>>
Color
=
namedtuple
(
'Color'
,
'red green blue'
)
>>>
Pixel
=
namedtuple
(
'Pixel'
,
Point
.
_fields
+
Color
.
_fields
)
>>>
Pixel
(
11
,
22
,
128
,
255
,
0
)
Pixel(x=11, y=22, red=128, green=255, blue=0)
somenamedtuple.
_field_defaults
¶
Dictionary mapping field names to default values.
>>>
Account
=
namedtuple
(
'Account'
,
[
'type'
,
'balance'
],
defaults
=
[
0
])
>>>
Account
.
_field_defaults
{'balance': 0}
>>>
Account
(
'premium'
)
Account(type='premium', balance=0)
To retrieve a field whose name is stored in a string, use the
getattr()
function:
>>>
getattr
(
p
,
'x'
)
11
To convert a dictionary to a named tuple, use the double-star-operator
(as described in
Unpacking Argument Lists
):
>>>
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 fixed-width print format:
>>>
class
Point
(
namedtuple
(
'Point'
,
[
'x'
,
'y'
])):
...
__slots__
=
()
...
@property
...
def
hypot
(
self
):
...
return
(
self
.
x
**
2
+
self
.
y
**
2
)
**
0.5
...
def
__str__
(
self
):
...
return
'Point: x=
%6.3f
y=
%6.3f
hypot=
%6.3f
'
%
(
self
.
x
,
self
.
y
,
self
.
hypot
)
>>>
for
p
in
Point
(
3
,
4
),
Point
(
14
,
5
/
7
):
...
print
(
p
)
Point: x= 3.000 y= 4.000 hypot= 5.000
Point: x=14.000 y= 0.714 hypot=14.018
The subclass shown above sets
__slots__
to an empty tuple. This helps
keep memory requirements low by preventing the creation of instance dictionaries.
Subclassing is not useful for adding new, stored fields. Instead, simply
create a new named tuple type from the
_fields
attribute:
>>>
Point3D
=
namedtuple
(
'Point3D'
,
Point
.
_fields
+
(
'z'
,))
Docstrings can be customized by making direct assignments to the
__doc__
fields:
>>>
Book
=
namedtuple
(
'Book'
,
[
'id'
,
'title'
,
'authors'
])
>>>
Book
.
__doc__
+=
': Hardcover book in active collection'
>>>
Book
.
id
.
__doc__
=
'13-digit ISBN'
>>>
Book
.
title
.
__doc__
=
'Title of first printing'
>>>
Book
.
authors
.
__doc__
=
'List of authors sorted by last name'
Changed in version 3.5:
Property docstrings became writeable.
See also
See
typing.NamedTuple
for a way to add type hints for named
tuples. It also provides an elegant notation using the
class
keyword:
class
Component
(
NamedTuple
):
part_number
:
int
weight
:
float
description
:
Optional
[
str
]
=
None
See
types.SimpleNamespace()
for a mutable namespace based on an
underlying dictionary instead of a tuple.
The
dataclasses
module provides a decorator and functions for
automatically adding generated special methods to user-defined classes.
OrderedDict
objects
¶
Ordered dictionaries are just like regular dictionaries but have some extra
capabilities relating to ordering operations. They have become less
important now that the built-in
dict
class gained the ability
to remember insertion order (this new behavior became guaranteed in
Python 3.7).
Some differences from
dict
still remain:
The regular
dict
was designed to be very good at mapping
operations. Tracking insertion order was secondary.
The
OrderedDict
was designed to be good at reordering operations.
Space efficiency, iteration speed, and the performance of update
operations were secondary.
The
OrderedDict
algorithm can handle frequent reordering operations
better than
dict
. As shown in the recipes below, this makes it
suitable for implementing various kinds of LRU caches.
The equality operation for
OrderedDict
checks for matching order.
A regular
dict
can emulate the order sensitive equality test with
p
==
q
and
all(k1
==
k2
for
k1,
k2
in
zip(p,
q))
.
The
popitem()
method of
OrderedDict
has a different
signature. It accepts an optional argument to specify which item is popped.
A regular
dict
can emulate OrderedDict’s
od.popitem(last=True)
with
d.popitem()
which is guaranteed to pop the rightmost (last) item.
A regular
dict
can emulate OrderedDict’s
od.popitem(last=False)
with
(k
:=
next(iter(d)),
d.pop(k))
which will return and remove the
leftmost (first) item if it exists.
OrderedDict
has a
move_to_end()
method to efficiently
reposition an element to an endpoint.
A regular
dict
can emulate OrderedDict’s
od.move_to_end(k,
last=True)
with
d[k]
=
d.pop(k)
which will move the key and its
associated value to the rightmost (last) position.
A regular
dict
does not have an efficient equivalent for
OrderedDict’s
od.move_to_end(k,
last=False)
which moves the key
and its associated value to the leftmost (first) position.
Until Python 3.8,
dict
lacked a
__reversed__()
method.
class
collections.
OrderedDict
(
**
kwargs
)
¶
class
collections.
OrderedDict
(
mapping
,
/
,
**
kwargs
)
class
collections.
OrderedDict
(
iterable
,
/
,
**
kwargs
)
Return an instance of a
dict
subclass that has methods
specialized for rearranging dictionary order.
Added in version 3.1.
popitem
(
last
=
True
)
¶
The
popitem()
method for ordered dictionaries returns and removes a
(key, value) pair. The pairs are returned in
LIFO
order if
last
is true
or
FIFO
order if false.
move_to_end
(
key
,
last
=
True
)
¶
Move an existing
key
to either end of an ordered dictionary. The item
is moved to the right end if
last
is true (the default) or to the
beginning if
last
is false. Raises
KeyError
if the
key
does
not exist:
>>>
d
=
OrderedDict
.
fromkeys
(
'abcde'
)
>>>
d
.
move_to_end
(
'b'
)
>>>
''
.
join
(
d
)
'acdeb'
>>>
d
.
move_to_end
(
'b'
,
last
=
False
)
>>>
''
.
join
(
d
)
'bacde'
Added in version 3.2.
In addition to the usual mapping methods, ordered dictionaries also support
reverse iteration using
reversed()
.
Equality tests between
OrderedDict
objects are order-sensitive
and are roughly equivalent to
list(od1.items())==list(od2.items())
.
Equality tests between
OrderedDict
objects and other
Mapping
objects are order-insensitive like regular
dictionaries. This allows
OrderedDict
objects to be substituted
anywhere a regular dictionary is used.
Changed in version 3.5:
The items, keys, and values
views
of
OrderedDict
now support reverse iteration using
reversed()
.
Changed in version 3.6:
With the acceptance of
PEP 468
, order is retained for keyword arguments
passed to the
OrderedDict
constructor and its
update()
method.
Changed in version 3.9:
Added merge (
|
) and update (
|=
) operators, specified in
PEP 584
.
OrderedDict
Examples and Recipes
¶
It is straightforward to create an ordered dictionary variant
that remembers the order the keys were
last
inserted.
If a new entry overwrites an existing entry, the
original insertion position is changed and moved to the end:
class
LastUpdatedOrderedDict
(
OrderedDict
):
'Store items in the order the keys were last added'
def
__setitem__
(
self
,
key
,
value
):
super
()
.
__setitem__
(
key
,
value
)
self
.
move_to_end
(
key
)
An
OrderedDict
would also be useful for implementing
variants of
functools.lru_cache()
:
from
collections
import
OrderedDict
from
time
import
time
class
TimeBoundedLRU
:
"LRU Cache that invalidates and refreshes old entries."
def
__init__
(
self
,
func
,
maxsize
=
128
,
maxage
=
30
):
self
.
cache
=
OrderedDict
()
# { args : (timestamp, result)}
self
.
func
=
func
self
.
maxsize
=
maxsize
self
.
maxage
=
maxage
def
__call__
(
self
,
*
args
):
if
args
in
self
.
cache
:
self
.
cache
.
move_to_end
(
args
)
timestamp
,
result
=
self
.
cache
[
args
]
if
time
()
-
timestamp
<=
self
.
maxage
:
return
result
result
=
self
.
func
(
*
args
)
self
.
cache
[
args
]
=
time
(),
result
if
len
(
self
.
cache
)
>
self
.
maxsize
:
self
.
cache
.
popitem
(
last
=
False
)
return
result
class
MultiHitLRUCache
:
""" LRU cache that defers caching a result until
it has been requested multiple times.
To avoid flushing the LRU cache with one-time requests,
we don't cache until a request has been made more than once.
"""
def
__init__
(
self
,
func
,
maxsize
=
128
,
maxrequests
=
4096
,
cache_after
=
1
):
self
.
requests
=
OrderedDict
()
# { uncached_key : request_count }
self
.
cache
=
OrderedDict
()
# { cached_key : function_result }
self
.
func
=
func
self
.
maxrequests
=
maxrequests
# max number of uncached requests
self
.
maxsize
=
maxsize
# max number of stored return values
self
.
cache_after
=
cache_after
def
__call__
(
self
,
*
args
):
if
args
in
self
.
cache
:
self
.
cache
.
move_to_end
(
args
)
return
self
.
cache
[
args
]
result
=
self
.
func
(
*
args
)
self
.
requests
[
args
]
=
self
.
requests
.
get
(
args
,
0
)
+
1
if
self
.
requests
[
args
]
<=
self
.
cache_after
:
self
.
requests
.
move_to_end
(
args
)
if
len
(
self
.
requests
)
>
self
.
maxrequests
:
self
.
requests
.
popitem
(
last
=
False
)
else
:
self
.
requests
.
pop
(
args
,
None
)
self
.
cache
[
args
]
=
result
if
len
(
self
.
cache
)
>
self
.
maxsize
:
self
.
cache
.
popitem
(
last
=
False
)
return
result
UserDict
objects
¶
The class,
UserDict
acts as a wrapper around dictionary objects.
The need for this class has been partially supplanted by the ability to
subclass directly from
dict
; however, this class can be easier
to work with because the underlying dictionary is accessible as an
attribute.
class
collections.
UserDict
(
**
kwargs
)
¶
class
collections.
UserDict
(
mapping
,
/
,
**
kwargs
)
class
collections.
UserDict
(
iterable
,
/
,
**
kwargs
)
Class that simulates a dictionary. The instance’s contents are kept in a
regular dictionary, which is accessible via the
data
attribute of
UserDict
instances. If arguments are provided, they are used to
initialize
data
, like a regular dictionary.
In addition to supporting the methods and operations of mappings,
UserDict
instances provide the following attribute:
data
¶
A real dictionary used to store the contents of the
UserDict
class.
UserList
objects
¶
This class acts as a wrapper around list objects. It is a useful base class
for your own list-like classes which can inherit from them and override
existing methods or add new ones. In this way, one can add new behaviors to
lists.
The need for this class has been partially supplanted by the ability to
subclass directly from
list
; however, this class can be easier
to work with because the underlying list is accessible as an attribute.
class
collections.
UserList
(
[
list
]
)
¶
Class that simulates a list. The instance’s contents are kept in a regular
list, which is accessible via the
data
attribute of
UserList
instances. The instance’s contents are initially set to a copy of
list
,
defaulting to the empty list
[]
.
list
can be any iterable, for
example a real Python list or a
UserList
object.
In addition to supporting the methods and operations of mutable sequences,
UserList
instances provide the following attribute:
data
¶
A real
list
object used to store the contents of the
UserList
class.
Subclassing requirements:
Subclasses of
UserList
are expected to
offer a constructor which can be called with either no arguments or one
argument. List operations which return a new sequence attempt to create an
instance of the actual implementation class. To do so, it assumes that the
constructor can be called with a single parameter, which is a sequence object
used as a data source.
If a derived class does not wish to comply with this requirement, all of the
special methods supported by this class will need to be overridden; please
consult the sources for information about the methods which need to be provided
in that case.
UserString
objects
¶
The class,
UserString
acts as a wrapper around string objects.
The need for this class has been partially supplanted by the ability to
subclass directly from
str
; however, this class can be easier
to work with because the underlying string is accessible as an
attribute.
class
collections.
UserString
(
seq
)
¶
Class that simulates a string object. The instance’s
content is kept in a regular string object, which is accessible via the
data
attribute of
UserString
instances. The instance’s
contents are initially set to a copy of
seq
. The
seq
argument can
be any object which can be converted into a string using the built-in
str()
function.
In addition to supporting the methods and operations of strings,
UserString
instances provide the following attribute:
data
¶
A real
str
object used to store the contents of the
UserString
class.
Changed in version 3.5:
New methods
__getnewargs__
,
__rmod__
,
casefold
,
format_map
,
isprintable
, and
maketrans
. | |||||||||
| Markdown | [](https://www.python.org/)
Theme
### [Table of Contents](https://docs.python.org/3/contents.html)
- [`collections` — Container datatypes](https://docs.python.org/3/library/collections.html)
- [`ChainMap` objects](https://docs.python.org/3/library/collections.html#chainmap-objects)
- [`ChainMap` Examples and Recipes](https://docs.python.org/3/library/collections.html#chainmap-examples-and-recipes)
- [`Counter` objects](https://docs.python.org/3/library/collections.html#counter-objects)
- [`deque` objects](https://docs.python.org/3/library/collections.html#deque-objects)
- [`deque` Recipes](https://docs.python.org/3/library/collections.html#deque-recipes)
- [`defaultdict` objects](https://docs.python.org/3/library/collections.html#defaultdict-objects)
- [`defaultdict` Examples](https://docs.python.org/3/library/collections.html#defaultdict-examples)
- [`namedtuple()` Factory Function for Tuples with Named Fields](https://docs.python.org/3/library/collections.html#namedtuple-factory-function-for-tuples-with-named-fields)
- [`OrderedDict` objects](https://docs.python.org/3/library/collections.html#ordereddict-objects)
- [`OrderedDict` Examples and Recipes](https://docs.python.org/3/library/collections.html#ordereddict-examples-and-recipes)
- [`UserDict` objects](https://docs.python.org/3/library/collections.html#userdict-objects)
- [`UserList` objects](https://docs.python.org/3/library/collections.html#userlist-objects)
- [`UserString` objects](https://docs.python.org/3/library/collections.html#userstring-objects)
#### Previous topic
[`calendar` — General calendar-related functions](https://docs.python.org/3/library/calendar.html "previous chapter")
#### Next topic
[`collections.abc` — Abstract Base Classes for Containers](https://docs.python.org/3/library/collections.abc.html "next chapter")
### This page
- [Report a bug](https://docs.python.org/3/bugs.html)
- [Improve this page](https://docs.python.org/3/improve-page.html?pagetitle=collections+%E2%80%94+Container+datatypes&pageurl=https%3A%2F%2Fdocs.python.org%2F3%2Flibrary%2Fcollections.html&pagesource=library%2Fcollections.rst)
- [Show source](https://github.com/python/cpython/blob/main/Doc/library/collections.rst?plain=1)
### Navigation
- [index](https://docs.python.org/3/genindex.html "General Index")
- [modules](https://docs.python.org/3/py-modindex.html "Python Module Index") \|
- [next](https://docs.python.org/3/library/collections.abc.html "collections.abc — Abstract Base Classes for Containers") \|
- [previous](https://docs.python.org/3/library/calendar.html "calendar — General calendar-related functions") \|
- 
- [Python](https://www.python.org/) »
- [3\.14.4 Documentation](https://docs.python.org/3/index.html) »
- [The Python Standard Library](https://docs.python.org/3/library/index.html) »
- [Data Types](https://docs.python.org/3/library/datatypes.html) »
- [`collections` — Container datatypes](https://docs.python.org/3/library/collections.html)
- \|
- Theme
\|
# `collections` — Container datatypes[¶](https://docs.python.org/3/library/collections.html#module-collections "Link to this heading")
**Source code:** [Lib/collections/\_\_init\_\_.py](https://github.com/python/cpython/tree/3.14/Lib/collections/__init__.py)
***
This module implements specialized container datatypes providing alternatives to Python’s general purpose built-in containers, [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict"), [`list`](https://docs.python.org/3/library/stdtypes.html#list "list"), [`set`](https://docs.python.org/3/library/stdtypes.html#set "set"), and [`tuple`](https://docs.python.org/3/library/stdtypes.html#tuple "tuple").
| | |
|---|---|
| [`namedtuple()`](https://docs.python.org/3/library/collections.html#collections.namedtuple "collections.namedtuple") | factory function for creating tuple subclasses with named fields |
| [`deque`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque") | list-like container with fast appends and pops on either end |
| [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") | dict-like class for creating a single view of multiple mappings |
| [`Counter`](https://docs.python.org/3/library/collections.html#collections.Counter "collections.Counter") | dict subclass for counting [hashable](https://docs.python.org/3/glossary.html#term-hashable) objects |
| [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") | dict subclass that remembers the order entries were added |
| [`defaultdict`](https://docs.python.org/3/library/collections.html#collections.defaultdict "collections.defaultdict") | dict subclass that calls a factory function to supply missing values |
| [`UserDict`](https://docs.python.org/3/library/collections.html#collections.UserDict "collections.UserDict") | wrapper around dictionary objects for easier dict subclassing |
| [`UserList`](https://docs.python.org/3/library/collections.html#collections.UserList "collections.UserList") | wrapper around list objects for easier list subclassing |
| [`UserString`](https://docs.python.org/3/library/collections.html#collections.UserString "collections.UserString") | wrapper around string objects for easier string subclassing |
## [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") objects[¶](https://docs.python.org/3/library/collections.html#chainmap-objects "Link to this heading")
Added in version 3.3.
A [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") class is provided for quickly linking a number of mappings so they can be treated as a single unit. It is often much faster than creating a new dictionary and running multiple [`update()`](https://docs.python.org/3/library/stdtypes.html#dict.update "dict.update") calls.
The class can be used to simulate nested scopes and is useful in templating.
*class* collections.ChainMap(*\*maps*)[¶](https://docs.python.org/3/library/collections.html#collections.ChainMap "Link to this definition")
A `ChainMap` groups multiple dicts or other mappings together to create a single, updateable view. If no *maps* are specified, a single empty dictionary is provided so that a new chain always has at least one mapping.
The underlying mappings are stored in a list. That list is public and can be accessed or updated using the *maps* attribute. There is no other state.
Lookups search the underlying mappings successively until a key is found. In contrast, writes, updates, and deletions only operate on the first mapping.
A `ChainMap` incorporates the underlying mappings by reference. So, if one of the underlying mappings gets updated, those changes will be reflected in `ChainMap`.
All of the usual dictionary methods are supported. In addition, there is a *maps* attribute, a method for creating new subcontexts, and a property for accessing all but the first mapping:
maps[¶](https://docs.python.org/3/library/collections.html#collections.ChainMap.maps "Link to this definition")
A user updateable list of mappings. The list is ordered from first-searched to last-searched. It is the only stored state and can be modified to change which mappings are searched. The list should always contain at least one mapping.
new\_child(*m\=None*, *\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.ChainMap.new_child "Link to this definition")
Returns a new `ChainMap` containing a new map followed by all of the maps in the current instance. If `m` is specified, it becomes the new map at the front of the list of mappings; if not specified, an empty dict is used, so that a call to `d.new_child()` is equivalent to: `ChainMap({}, *d.maps)`. If any keyword arguments are specified, they update passed map or new empty dict. This method is used for creating subcontexts that can be updated without altering values in any of the parent mappings.
Changed in version 3.4: The optional `m` parameter was added.
Changed in version 3.10: Keyword arguments support was added.
parents[¶](https://docs.python.org/3/library/collections.html#collections.ChainMap.parents "Link to this definition")
Property returning a new `ChainMap` containing all of the maps in the current instance except the first one. This is useful for skipping the first map in the search. Use cases are similar to those for the [`nonlocal`](https://docs.python.org/3/reference/simple_stmts.html#nonlocal) keyword used in [nested scopes](https://docs.python.org/3/glossary.html#term-nested-scope). The use cases also parallel those for the built-in [`super()`](https://docs.python.org/3/library/functions.html#super "super") function. A reference to `d.parents` is equivalent to: `ChainMap(*d.maps[1:])`.
Note, the iteration order of a `ChainMap` is determined by scanning the mappings last to first:
Copy
```
>>> baseline = {'music': 'bach', 'art': 'rembrandt'}
>>> adjustments = {'art': 'van gogh', 'opera': 'carmen'}
>>> list(ChainMap(adjustments, baseline))
['music', 'art', 'opera']
```
This gives the same ordering as a series of [`dict.update()`](https://docs.python.org/3/library/stdtypes.html#dict.update "dict.update") calls starting with the last mapping:
Copy
```
>>> combined = baseline.copy()
>>> combined.update(adjustments)
>>> list(combined)
['music', 'art', 'opera']
```
Changed in version 3.9: Added support for `|` and `|=` operators, specified in [**PEP 584**](https://peps.python.org/pep-0584/).
See also
- The [MultiContext class](https://github.com/enthought/codetools/blob/4.0.0/codetools/contexts/multi_context.py) in the Enthought [CodeTools package](https://github.com/enthought/codetools) has options to support writing to any mapping in the chain.
- Django’s [Context class](https://github.com/django/django/blob/main/django/template/context.py) for templating is a read-only chain of mappings. It also features pushing and popping of contexts similar to the [`new_child()`](https://docs.python.org/3/library/collections.html#collections.ChainMap.new_child "collections.ChainMap.new_child") method and the [`parents`](https://docs.python.org/3/library/collections.html#collections.ChainMap.parents "collections.ChainMap.parents") property.
- The [Nested Contexts recipe](https://code.activestate.com/recipes/577434-nested-contexts-a-chain-of-mapping-objects/) has options to control whether writes and other mutations apply only to the first mapping or to any mapping in the chain.
- A [greatly simplified read-only version of Chainmap](https://code.activestate.com/recipes/305268/).
### [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") Examples and Recipes[¶](https://docs.python.org/3/library/collections.html#chainmap-examples-and-recipes "Link to this heading")
This section shows various approaches to working with chained maps.
Example of simulating Python’s internal lookup chain:
Copy
```
import builtins
pylookup = ChainMap(locals(), globals(), vars(builtins))
```
Example of letting user specified command-line arguments take precedence over environment variables which in turn take precedence over default values:
Copy
```
import os, argparse
defaults = {'color': 'red', 'user': 'guest'}
parser = argparse.ArgumentParser()
parser.add_argument('-u', '--user')
parser.add_argument('-c', '--color')
namespace = parser.parse_args()
command_line_args = {k: v for k, v in vars(namespace).items() if v is not None}
combined = ChainMap(command_line_args, os.environ, defaults)
print(combined['color'])
print(combined['user'])
```
Example patterns for using the [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") class to simulate nested contexts:
Copy
```
c = ChainMap() # Create root context
d = c.new_child() # Create nested child context
e = c.new_child() # Child of c, independent from d
e.maps[0] # Current context dictionary -- like Python's locals()
e.maps[-1] # Root context -- like Python's globals()
e.parents # Enclosing context chain -- like Python's nonlocals
d['x'] = 1 # Set value in current context
d['x'] # Get first key in the chain of contexts
del d['x'] # Delete from current context
list(d) # All nested values
k in d # Check all nested values
len(d) # Number of nested values
d.items() # All nested items
dict(d) # Flatten into a regular dictionary
```
The [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") class only makes updates (writes and deletions) to the first mapping in the chain while lookups will search the full chain. However, if deep writes and deletions are desired, it is easy to make a subclass that updates keys found deeper in the chain:
Copy
```
class DeepChainMap(ChainMap):
'Variant of ChainMap that allows direct updates to inner scopes'
def __setitem__(self, key, value):
for mapping in self.maps:
if key in mapping:
mapping[key] = value
return
self.maps[0][key] = value
def __delitem__(self, key):
for mapping in self.maps:
if key in mapping:
del mapping[key]
return
raise KeyError(key)
>>> d = DeepChainMap({'zebra': 'black'}, {'elephant': 'blue'}, {'lion': 'yellow'})
>>> d['lion'] = 'orange' # update an existing key two levels down
>>> d['snake'] = 'red' # new keys get added to the topmost dict
>>> del d['elephant'] # remove an existing key one level down
>>> d # display result
DeepChainMap({'zebra': 'black', 'snake': 'red'}, {}, {'lion': 'orange'})
```
## [`Counter`](https://docs.python.org/3/library/collections.html#collections.Counter "collections.Counter") objects[¶](https://docs.python.org/3/library/collections.html#counter-objects "Link to this heading")
A counter tool is provided to support convenient and rapid tallies. For example:
Copy
```
>>> # Tally occurrences of words in a list
>>> cnt = Counter()
>>> for word in ['red', 'blue', 'red', 'green', 'blue', 'blue']:
... cnt[word] += 1
...
>>> cnt
Counter({'blue': 3, 'red': 2, 'green': 1})
>>> # Find the ten most common words in Hamlet
>>> import re
>>> words = re.findall(r'\w+', open('hamlet.txt').read().lower())
>>> Counter(words).most_common(10)
[('the', 1143), ('and', 966), ('to', 762), ('of', 669), ('i', 631),
('you', 554), ('a', 546), ('my', 514), ('hamlet', 471), ('in', 451)]
```
*class* collections.Counter(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.Counter "Link to this definition")
*class* collections.Counter(*iterable*, */*, *\*\*kwargs*)
*class* collections.Counter(*mapping*, */*, *\*\*kwargs*)
A `Counter` is a [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") subclass for counting [hashable](https://docs.python.org/3/glossary.html#term-hashable) objects. It is a collection where elements are stored as dictionary keys and their counts are stored as dictionary values. Counts are allowed to be any integer value including zero or negative counts. The `Counter` class is similar to bags or multisets in other languages.
Elements are counted from an *iterable* or initialized from another *mapping* (or counter):
Copy
```
>>> c = Counter() # a new, empty counter
>>> c = Counter('gallahad') # a new counter from an iterable
>>> c = Counter({'red': 4, 'blue': 2}) # a new counter from a mapping
>>> c = Counter(cats=4, dogs=8) # a new counter from keyword args
```
Counter objects have a dictionary interface except that they return a zero count for missing items instead of raising a [`KeyError`](https://docs.python.org/3/library/exceptions.html#KeyError "KeyError"):
Copy
```
>>> c = Counter(['eggs', 'ham'])
>>> c['bacon'] # count of a missing element is zero
0
```
Setting a count to zero does not remove an element from a counter. Use `del` to remove it entirely:
Copy
```
>>> c['sausage'] = 0 # counter entry with a zero count
>>> del c['sausage'] # del actually removes the entry
```
Added in version 3.1.
Changed in version 3.7: As a [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") subclass, `Counter` inherited the capability to remember insertion order. Math operations on *Counter* objects also preserve order. Results are ordered according to when an element is first encountered in the left operand and then by the order encountered in the right operand.
Counter objects support additional methods beyond those available for all dictionaries:
elements()[¶](https://docs.python.org/3/library/collections.html#collections.Counter.elements "Link to this definition")
Return an iterator over elements repeating each as many times as its count. Elements are returned in the order first encountered. If an element’s count is less than one, `elements()` will ignore it.
Copy
```
>>> c = Counter(a=4, b=2, c=0, d=-2)
>>> sorted(c.elements())
['a', 'a', 'a', 'a', 'b', 'b']
```
most\_common(*n\=None*)[¶](https://docs.python.org/3/library/collections.html#collections.Counter.most_common "Link to this definition")
Return a list of the *n* most common elements and their counts from the most common to the least. If *n* is omitted or `None`, `most_common()` returns *all* elements in the counter. Elements with equal counts are ordered in the order first encountered:
Copy
```
>>> Counter('abracadabra').most_common(3)
[('a', 5), ('b', 2), ('r', 2)]
```
subtract(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.Counter.subtract "Link to this definition")
subtract(*iterable*, */*, *\*\*kwargs*)
subtract(*mapping*, */*, *\*\*kwargs*)
Elements are subtracted from an *iterable* or from another *mapping* (or counter). Like [`dict.update()`](https://docs.python.org/3/library/stdtypes.html#dict.update "dict.update") but subtracts counts instead of replacing them. Both inputs and outputs may be zero or negative.
Copy
```
>>> c = Counter(a=4, b=2, c=0, d=-2)
>>> d = Counter(a=1, b=2, c=3, d=4)
>>> c.subtract(d)
>>> c
Counter({'a': 3, 'b': 0, 'c': -3, 'd': -6})
```
Added in version 3.2.
total()[¶](https://docs.python.org/3/library/collections.html#collections.Counter.total "Link to this definition")
Compute the sum of the counts.
Copy
```
>>> c = Counter(a=10, b=5, c=0)
>>> c.total()
15
```
Added in version 3.10.
The usual dictionary methods are available for `Counter` objects except for two which work differently for counters.
fromkeys(*iterable*)[¶](https://docs.python.org/3/library/collections.html#collections.Counter.fromkeys "Link to this definition")
This class method is not implemented for `Counter` objects.
update(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.Counter.update "Link to this definition")
update(*iterable*, */*, *\*\*kwargs*)
update(*mapping*, */*, *\*\*kwargs*)
Elements are counted from an *iterable* or added-in from another *mapping* (or counter). Like [`dict.update()`](https://docs.python.org/3/library/stdtypes.html#dict.update "dict.update") but adds counts instead of replacing them. Also, the *iterable* is expected to be a sequence of elements, not a sequence of `(key, value)` pairs.
Counters support rich comparison operators for equality, subset, and superset relationships: `==`, `!=`, `<`, `<=`, `>`, `>=`. All of those tests treat missing elements as having zero counts so that `Counter(a=1) == Counter(a=1, b=0)` returns true.
Changed in version 3.10: Rich comparison operations were added.
Changed in version 3.10: In equality tests, missing elements are treated as having zero counts. Formerly, `Counter(a=3)` and `Counter(a=3, b=0)` were considered distinct.
Common patterns for working with [`Counter`](https://docs.python.org/3/library/collections.html#collections.Counter "collections.Counter") objects:
Copy
```
c.total() # total of all counts
c.clear() # reset all counts
list(c) # list unique elements
set(c) # convert to a set
dict(c) # convert to a regular dictionary
c.items() # access the (elem, cnt) pairs
Counter(dict(list_of_pairs)) # convert from a list of (elem, cnt) pairs
c.most_common()[:-n-1:-1] # n least common elements
+c # remove zero and negative counts
```
Several mathematical operations are provided for combining [`Counter`](https://docs.python.org/3/library/collections.html#collections.Counter "collections.Counter") objects to produce multisets (counters that have counts greater than zero). Addition and subtraction combine counters by adding or subtracting the counts of corresponding elements. Intersection and union return the minimum and maximum of corresponding counts. Equality and inclusion compare corresponding counts. Each operation can accept inputs with signed counts, but the output will exclude results with counts of zero or less.
Copy
```
>>> c = Counter(a=3, b=1)
>>> d = Counter(a=1, b=2)
>>> c + d # add two counters together: c[x] + d[x]
Counter({'a': 4, 'b': 3})
>>> c - d # subtract (keeping only positive counts)
Counter({'a': 2})
>>> c & d # intersection: min(c[x], d[x])
Counter({'a': 1, 'b': 1})
>>> c | d # union: max(c[x], d[x])
Counter({'a': 3, 'b': 2})
>>> c == d # equality: c[x] == d[x]
False
>>> c <= d # inclusion: c[x] <= d[x]
False
```
Unary addition and subtraction are shortcuts for adding an empty counter or subtracting from an empty counter.
Copy
```
>>> c = Counter(a=2, b=-4)
>>> +c
Counter({'a': 2})
>>> -c
Counter({'b': 4})
```
Added in version 3.3: Added support for unary plus, unary minus, and in-place multiset operations.
Note
Counters were primarily designed to work with positive integers to represent running counts; however, care was taken to not unnecessarily preclude use cases needing other types or negative values. To help with those use cases, this section documents the minimum range and type restrictions.
- The [`Counter`](https://docs.python.org/3/library/collections.html#collections.Counter "collections.Counter") class itself is a dictionary subclass with no restrictions on its keys and values. The values are intended to be numbers representing counts, but you *could* store anything in the value field.
- The [`most_common()`](https://docs.python.org/3/library/collections.html#collections.Counter.most_common "collections.Counter.most_common") method requires only that the values be orderable.
- For in-place operations such as `c[key] += 1`, the value type need only support addition and subtraction. So fractions, floats, and decimals would work and negative values are supported. The same is also true for [`update()`](https://docs.python.org/3/library/collections.html#collections.Counter.update "collections.Counter.update") and [`subtract()`](https://docs.python.org/3/library/collections.html#collections.Counter.subtract "collections.Counter.subtract") which allow negative and zero values for both inputs and outputs.
- The multiset methods are designed only for use cases with positive values. The inputs may be negative or zero, but only outputs with positive values are created. There are no type restrictions, but the value type needs to support addition, subtraction, and comparison.
- The [`elements()`](https://docs.python.org/3/library/collections.html#collections.Counter.elements "collections.Counter.elements") method requires integer counts. It ignores zero and negative counts.
See also
- [Bag class](https://www.gnu.org/software/smalltalk/manual-base/html_node/Bag.html) in Smalltalk.
- Wikipedia entry for [Multisets](https://en.wikipedia.org/wiki/Multiset).
- [C++ multisets](http://www.java2s.com/Tutorial/Cpp/0380__set-multiset/Catalog0380__set-multiset.htm) tutorial with examples.
- For mathematical operations on multisets and their use cases, see *Knuth, Donald. The Art of Computer Programming Volume II, Section 4.6.3, Exercise 19*.
- To enumerate all distinct multisets of a given size over a given set of elements, see [`itertools.combinations_with_replacement()`](https://docs.python.org/3/library/itertools.html#itertools.combinations_with_replacement "itertools.combinations_with_replacement"):
Copy
```
map(Counter, combinations_with_replacement('ABC', 2)) # --> AA AB AC BB BC CC
```
## [`deque`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque") objects[¶](https://docs.python.org/3/library/collections.html#deque-objects "Link to this heading")
*class* collections.deque(\[*iterable*\[, *maxlen*\]\])[¶](https://docs.python.org/3/library/collections.html#collections.deque "Link to this definition")
Returns a new deque object initialized left-to-right (using [`append()`](https://docs.python.org/3/library/collections.html#collections.deque.append "collections.deque.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 [`list`](https://docs.python.org/3/library/stdtypes.html#list "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.
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.
Deque objects support the following methods:
append(*item*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.append "Link to this definition")
Add *item* to the right side of the deque.
appendleft(*item*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.appendleft "Link to this definition")
Add *item* to the left side of the deque.
clear()[¶](https://docs.python.org/3/library/collections.html#collections.deque.clear "Link to this definition")
Remove all elements from the deque leaving it with length 0.
copy()[¶](https://docs.python.org/3/library/collections.html#collections.deque.copy "Link to this definition")
Create a shallow copy of the deque.
Added in version 3.5.
count(*value*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.count "Link to this definition")
Count the number of deque elements equal to *value*.
Added in version 3.2.
extend(*iterable*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.extend "Link to this definition")
Extend the right side of the deque by appending elements from the iterable argument.
extendleft(*iterable*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.extendleft "Link to this definition")
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.
index(*value*\[, *start*\[, *stop*\]\])[¶](https://docs.python.org/3/library/collections.html#collections.deque.index "Link to this definition")
Return the position of *value* in the deque (at or after index *start* and before index *stop*). Returns the first match or raises [`ValueError`](https://docs.python.org/3/library/exceptions.html#ValueError "ValueError") if not found.
Added in version 3.5.
insert(*index*, *value*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.insert "Link to this definition")
Insert *value* into the deque at position *index*.
If the insertion would cause a bounded deque to grow beyond *maxlen*, an [`IndexError`](https://docs.python.org/3/library/exceptions.html#IndexError "IndexError") is raised.
Added in version 3.5.
pop()[¶](https://docs.python.org/3/library/collections.html#collections.deque.pop "Link to this definition")
Remove and return an element from the right side of the deque. If no elements are present, raises an [`IndexError`](https://docs.python.org/3/library/exceptions.html#IndexError "IndexError").
popleft()[¶](https://docs.python.org/3/library/collections.html#collections.deque.popleft "Link to this definition")
Remove and return an element from the left side of the deque. If no elements are present, raises an [`IndexError`](https://docs.python.org/3/library/exceptions.html#IndexError "IndexError").
remove(*value*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.remove "Link to this definition")
Remove the first occurrence of *value*. If not found, raises a [`ValueError`](https://docs.python.org/3/library/exceptions.html#ValueError "ValueError").
reverse()[¶](https://docs.python.org/3/library/collections.html#collections.deque.reverse "Link to this definition")
Reverse the elements of the deque in-place and then return `None`.
Added in version 3.2.
rotate(*n\=1*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.rotate "Link to this definition")
Rotate the deque *n* steps to the right. If *n* is negative, rotate to the left.
When the deque is not empty, rotating one step to the right is equivalent to `d.appendleft(d.pop())`, and rotating one step to the left is equivalent to `d.append(d.popleft())`.
Deque objects also provide one read-only attribute:
maxlen[¶](https://docs.python.org/3/library/collections.html#collections.deque.maxlen "Link to this definition")
Maximum size of a deque or `None` if unbounded.
Added in version 3.1.
In addition to the above, deques support iteration, pickling, `len(d)`, `reversed(d)`, `copy.copy(d)`, `copy.deepcopy(d)`, membership testing with the [`in`](https://docs.python.org/3/reference/expressions.html#in) operator, and subscript references such as `d[0]` to access the first element. Indexed access is *O*(1) at both ends but slows to *O*(*n*) in the middle. For fast random access, use lists instead.
Starting in version 3.5, deques support `__add__()`, `__mul__()`, and `__imul__()`.
Example:
Copy
```
>>> 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`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque") Recipes[¶](https://docs.python.org/3/library/collections.html#deque-recipes "Link to this heading")
This section shows various approaches to working with deques.
Bounded length deques provide functionality similar to the `tail` filter in Unix:
Copy
```
def tail(filename, n=10):
'Return the last n lines of a file'
with open(filename) as f:
return deque(f, n)
```
Another approach to using deques is to maintain a sequence of recently added elements by appending to the right and popping to the left:
Copy
```
def moving_average(iterable, n=3):
# moving_average([40, 30, 50, 46, 39, 44]) --> 40.0 42.0 45.0 43.0
# https://en.wikipedia.org/wiki/Moving_average
it = iter(iterable)
d = deque(itertools.islice(it, n-1))
d.appendleft(0)
s = sum(d)
for elem in it:
s += elem - d.popleft()
d.append(elem)
yield s / n
```
A [round-robin scheduler](https://en.wikipedia.org/wiki/Round-robin_scheduling) can be implemented with input iterators stored in a [`deque`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque"). Values are yielded from the active iterator in position zero. If that iterator is exhausted, it can be removed with [`popleft()`](https://docs.python.org/3/library/collections.html#collections.deque.popleft "collections.deque.popleft"); otherwise, it can be cycled back to the end with the [`rotate()`](https://docs.python.org/3/library/collections.html#collections.deque.rotate "collections.deque.rotate") method:
Copy
```
def roundrobin(*iterables):
"roundrobin('ABC', 'D', 'EF') --> A D E B F C"
iterators = deque(map(iter, iterables))
while iterators:
try:
while True:
yield next(iterators[0])
iterators.rotate(-1)
except StopIteration:
# Remove an exhausted iterator.
iterators.popleft()
```
The [`rotate()`](https://docs.python.org/3/library/collections.html#collections.deque.rotate "collections.deque.rotate") method provides a way to implement [`deque`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque") slicing and deletion. For example, a pure Python implementation of `del d[n]` relies on the `rotate()` method to position elements to be popped:
Copy
```
def delete_nth(d, n):
d.rotate(-n)
d.popleft()
d.rotate(n)
```
To implement [`deque`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque") slicing, use a similar approach applying [`rotate()`](https://docs.python.org/3/library/collections.html#collections.deque.rotate "collections.deque.rotate") to bring a target element to the left side of the deque. Remove old entries with [`popleft()`](https://docs.python.org/3/library/collections.html#collections.deque.popleft "collections.deque.popleft"), add new entries with [`extend()`](https://docs.python.org/3/library/collections.html#collections.deque.extend "collections.deque.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`.
## [`defaultdict`](https://docs.python.org/3/library/collections.html#collections.defaultdict "collections.defaultdict") objects[¶](https://docs.python.org/3/library/collections.html#defaultdict-objects "Link to this heading")
*class* collections.defaultdict(*default\_factory\=None*, */*, *\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.defaultdict "Link to this definition")
*class* collections.defaultdict(*default\_factory*, *mapping*, */*, *\*\*kwargs*)
*class* collections.defaultdict(*default\_factory*, *iterable*, */*, *\*\*kwargs*)
Return a new dictionary-like object. `defaultdict` is a subclass of the built-in [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") class. It overrides one method and adds one writable instance variable. The remaining functionality is the same as for the `dict` class and is not documented here.
The first argument provides the initial value for the [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") attribute; it defaults to `None`. All remaining arguments are treated the same as if they were passed to the [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") constructor, including keyword arguments.
`defaultdict` objects support the following method in addition to the standard [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") operations:
\_\_missing\_\_(*key*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.defaultdict.__missing__ "Link to this definition")
If the [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") attribute is `None`, this raises a [`KeyError`](https://docs.python.org/3/library/exceptions.html#KeyError "KeyError") exception with the *key* as argument.
If [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.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 [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") raises an exception this exception is propagated unchanged.
This method is called by the [`__getitem__()`](https://docs.python.org/3/reference/datamodel.html#object.__getitem__ "object.__getitem__") method of the [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") class when the requested key is not found; whatever it returns or raises is then returned or raised by `__getitem__()`.
Note that `__missing__()` is *not* called for any operations besides [`__getitem__()`](https://docs.python.org/3/reference/datamodel.html#object.__getitem__ "object.__getitem__"). This means that [`get()`](https://docs.python.org/3/library/stdtypes.html#dict.get "dict.get") will, like normal dictionaries, return `None` as a default rather than using [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory").
`defaultdict` objects support the following instance variable:
default\_factory[¶](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "Link to this definition")
This attribute is used by the [`__missing__()`](https://docs.python.org/3/library/collections.html#collections.defaultdict.__missing__ "collections.defaultdict.__missing__") method; it is initialized from the first argument to the constructor, if present, or to `None`, if absent.
Changed in version 3.9: Added merge (`|`) and update (`|=`) operators, specified in [**PEP 584**](https://peps.python.org/pep-0584/).
### [`defaultdict`](https://docs.python.org/3/library/collections.html#collections.defaultdict "collections.defaultdict") Examples[¶](https://docs.python.org/3/library/collections.html#defaultdict-examples "Link to this heading")
Using [`list`](https://docs.python.org/3/library/stdtypes.html#list "list") as the [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory"), it is easy to group a sequence of key-value pairs into a dictionary of lists:
Copy
```
>>> s = [('yellow', 1), ('blue', 2), ('yellow', 3), ('blue', 4), ('red', 1)]
>>> d = defaultdict(list)
>>> for k, v in s:
... d[k].append(v)
...
>>> sorted(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 [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") function which returns an empty [`list`](https://docs.python.org/3/library/stdtypes.html#list "list"). The [`list.append()`](https://docs.python.org/3/library/stdtypes.html#list.append "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 `list.append()` operation adds another value to the list. This technique is simpler and faster than an equivalent technique using [`dict.setdefault()`](https://docs.python.org/3/library/stdtypes.html#dict.setdefault "dict.setdefault"):
Copy
```
>>> d = {}
>>> for k, v in s:
... d.setdefault(k, []).append(v)
...
>>> sorted(d.items())
[('blue', [2, 4]), ('red', [1]), ('yellow', [1, 3])]
```
Setting the [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") to [`int`](https://docs.python.org/3/library/functions.html#int "int") makes the [`defaultdict`](https://docs.python.org/3/library/collections.html#collections.defaultdict "collections.defaultdict") useful for counting (like a bag or multiset in other languages):
Copy
```
>>> s = 'mississippi'
>>> d = defaultdict(int)
>>> for k in s:
... d[k] += 1
...
>>> sorted(d.items())
[('i', 4), ('m', 1), ('p', 2), ('s', 4)]
```
When a letter is first encountered, it is missing from the mapping, so the [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") function calls [`int()`](https://docs.python.org/3/library/functions.html#int "int") to supply a default count of zero. The increment operation then builds up the count for each letter.
The function [`int()`](https://docs.python.org/3/library/functions.html#int "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 a lambda function which can supply any constant value (not just zero):
Copy
```
>>> def constant_factory(value):
... return lambda: value
...
>>> 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 [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") to [`set`](https://docs.python.org/3/library/stdtypes.html#set "set") makes the [`defaultdict`](https://docs.python.org/3/library/collections.html#collections.defaultdict "collections.defaultdict") useful for building a dictionary of sets:
Copy
```
>>> 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)
...
>>> sorted(d.items())
[('blue', {2, 4}), ('red', {1, 3})]
```
## [`namedtuple()`](https://docs.python.org/3/library/collections.html#collections.namedtuple "collections.namedtuple") Factory Function for Tuples with Named Fields[¶](https://docs.python.org/3/library/collections.html#namedtuple-factory-function-for-tuples-with-named-fields "Link to this heading")
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.
collections.namedtuple(*typename*, *field\_names*, *\**, *rename\=False*, *defaults\=None*, *module\=None*)[¶](https://docs.python.org/3/library/collections.html#collections.namedtuple "Link to this definition")
Returns a new tuple subclass named *typename*. The new subclass is used to create tuple-like objects that have fields accessible by attribute lookup as well as being indexable and iterable. Instances of the subclass also have a helpful docstring (with *typename* and *field\_names*) and a helpful [`__repr__()`](https://docs.python.org/3/reference/datamodel.html#object.__repr__ "object.__repr__") method which lists the tuple contents in a `name=value` format.
The *field\_names* are a sequence of strings such as `['x', 'y']`. Alternatively, *field\_names* can be a single string with each fieldname separated by whitespace and/or commas, for example `'x y'` or `'x, y'`.
Any valid Python identifier may be used for a fieldname except for names starting with an underscore. Valid identifiers consist of letters, digits, and underscores but do not start with a digit or underscore and cannot be a [`keyword`](https://docs.python.org/3/library/keyword.html#module-keyword "keyword: Test whether a string is a keyword in Python.") such as *class*, *for*, *return*, *global*, *pass*, or *raise*.
If *rename* is true, invalid fieldnames are automatically replaced with positional names. For example, `['abc', 'def', 'ghi', 'abc']` is converted to `['abc', '_1', 'ghi', '_3']`, eliminating the keyword `def` and the duplicate fieldname `abc`.
*defaults* can be `None` or an [iterable](https://docs.python.org/3/glossary.html#term-iterable) of default values. Since fields with a default value must come after any fields without a default, the *defaults* are applied to the rightmost parameters. For example, if the fieldnames are `['x', 'y', 'z']` and the defaults are `(1, 2)`, then `x` will be a required argument, `y` will default to `1`, and `z` will default to `2`.
If *module* is defined, the [`__module__`](https://docs.python.org/3/reference/datamodel.html#type.__module__ "type.__module__") attribute of the named tuple is set to that value.
Named tuple instances do not have per-instance dictionaries, so they are lightweight and require no more memory than regular tuples.
To support pickling, the named tuple class should be assigned to a variable that matches *typename*.
Changed in version 3.1: Added support for *rename*.
Changed in version 3.6: The *verbose* and *rename* parameters became [keyword-only arguments](https://docs.python.org/3/glossary.html#keyword-only-parameter).
Changed in version 3.6: Added the *module* parameter.
Changed in version 3.7: Removed the *verbose* parameter and the `_source` attribute.
Changed in version 3.7: Added the *defaults* parameter and the [`_field_defaults`](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._field_defaults "collections.somenamedtuple._field_defaults") attribute.
Copy
```
>>> # Basic example
>>> Point = namedtuple('Point', ['x', 'y'])
>>> p = Point(11, y=22) # instantiate with positional or keyword arguments
>>> p[0] + p[1] # indexable like the plain tuple (11, 22)
33
>>> x, y = p # unpack like a regular tuple
>>> x, y
(11, 22)
>>> p.x + p.y # fields also accessible 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 [`csv`](https://docs.python.org/3/library/csv.html#module-csv "csv: Write and read tabular data to and from delimited files.") or [`sqlite3`](https://docs.python.org/3/library/sqlite3.html#module-sqlite3 "sqlite3: A DB-API 2.0 implementation using SQLite 3.x.") modules:
Copy
```
EmployeeRecord = namedtuple('EmployeeRecord', 'name, age, title, department, paygrade')
import csv
for emp in map(EmployeeRecord._make, csv.reader(open("employees.csv", "rb"))):
print(emp.name, emp.title)
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()):
print(emp.name, emp.title)
```
In addition to the methods inherited from tuples, named tuples support three additional methods and two attributes. To prevent conflicts with field names, the method and attribute names start with an underscore.
*classmethod* somenamedtuple.\_make(*iterable*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._make "Link to this definition")
Class method that makes a new instance from an existing sequence or iterable.
Copy
```
>>> t = [11, 22]
>>> Point._make(t)
Point(x=11, y=22)
```
somenamedtuple.\_asdict()[¶](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._asdict "Link to this definition")
Return a new [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") which maps field names to their corresponding values:
Copy
```
>>> p = Point(x=11, y=22)
>>> p._asdict()
{'x': 11, 'y': 22}
```
Changed in version 3.1: Returns an [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") instead of a regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict").
Changed in version 3.8: Returns a regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") instead of an [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict"). As of Python 3.7, regular dicts are guaranteed to be ordered. If the extra features of `OrderedDict` are required, the suggested remediation is to cast the result to the desired type: `OrderedDict(nt._asdict())`.
somenamedtuple.\_replace(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._replace "Link to this definition")
Return a new instance of the named tuple replacing specified fields with new values:
Copy
```
>>> p = Point(x=11, y=22)
>>> p._replace(x=33)
Point(x=33, y=22)
>>> for partnum, record in inventory.items():
... inventory[partnum] = record._replace(price=newprices[partnum], timestamp=time.now())
```
Named tuples are also supported by generic function [`copy.replace()`](https://docs.python.org/3/library/copy.html#copy.replace "copy.replace").
Changed in version 3.13: Raise [`TypeError`](https://docs.python.org/3/library/exceptions.html#TypeError "TypeError") instead of [`ValueError`](https://docs.python.org/3/library/exceptions.html#ValueError "ValueError") for invalid keyword arguments.
somenamedtuple.\_fields[¶](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._fields "Link to this definition")
Tuple of strings listing the field names. Useful for introspection and for creating new named tuple types from existing named tuples.
Copy
```
>>> p._fields # view the field names
('x', 'y')
>>> Color = namedtuple('Color', 'red green blue')
>>> Pixel = namedtuple('Pixel', Point._fields + Color._fields)
>>> Pixel(11, 22, 128, 255, 0)
Pixel(x=11, y=22, red=128, green=255, blue=0)
```
somenamedtuple.\_field\_defaults[¶](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._field_defaults "Link to this definition")
Dictionary mapping field names to default values.
Copy
```
>>> Account = namedtuple('Account', ['type', 'balance'], defaults=[0])
>>> Account._field_defaults
{'balance': 0}
>>> Account('premium')
Account(type='premium', balance=0)
```
To retrieve a field whose name is stored in a string, use the [`getattr()`](https://docs.python.org/3/library/functions.html#getattr "getattr") function:
Copy
```
>>> getattr(p, 'x')
11
```
To convert a dictionary to a named tuple, use the double-star-operator (as described in [Unpacking Argument Lists](https://docs.python.org/3/tutorial/controlflow.html#tut-unpacking-arguments)):
Copy
```
>>> 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 fixed-width print format:
Copy
```
>>> class Point(namedtuple('Point', ['x', 'y'])):
... __slots__ = ()
... @property
... def hypot(self):
... return (self.x ** 2 + self.y ** 2) ** 0.5
... def __str__(self):
... return 'Point: x=%6.3f y=%6.3f hypot=%6.3f' % (self.x, self.y, self.hypot)
>>> for p in Point(3, 4), Point(14, 5/7):
... print(p)
Point: x= 3.000 y= 4.000 hypot= 5.000
Point: x=14.000 y= 0.714 hypot=14.018
```
The subclass shown above sets `__slots__` to an empty tuple. This helps keep memory requirements low by preventing the creation of instance dictionaries.
Subclassing is not useful for adding new, stored fields. Instead, simply create a new named tuple type from the [`_fields`](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._fields "collections.somenamedtuple._fields") attribute:
Copy
```
>>> Point3D = namedtuple('Point3D', Point._fields + ('z',))
```
Docstrings can be customized by making direct assignments to the `__doc__` fields:
Copy
```
>>> Book = namedtuple('Book', ['id', 'title', 'authors'])
>>> Book.__doc__ += ': Hardcover book in active collection'
>>> Book.id.__doc__ = '13-digit ISBN'
>>> Book.title.__doc__ = 'Title of first printing'
>>> Book.authors.__doc__ = 'List of authors sorted by last name'
```
Changed in version 3.5: Property docstrings became writeable.
See also
- See [`typing.NamedTuple`](https://docs.python.org/3/library/typing.html#typing.NamedTuple "typing.NamedTuple") for a way to add type hints for named tuples. It also provides an elegant notation using the [`class`](https://docs.python.org/3/reference/compound_stmts.html#class) keyword:
Copy
```
class Component(NamedTuple):
part_number: int
weight: float
description: Optional[str] = None
```
- See [`types.SimpleNamespace()`](https://docs.python.org/3/library/types.html#types.SimpleNamespace "types.SimpleNamespace") for a mutable namespace based on an underlying dictionary instead of a tuple.
- The [`dataclasses`](https://docs.python.org/3/library/dataclasses.html#module-dataclasses "dataclasses: Generate special methods on user-defined classes.") module provides a decorator and functions for automatically adding generated special methods to user-defined classes.
## [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") objects[¶](https://docs.python.org/3/library/collections.html#ordereddict-objects "Link to this heading")
Ordered dictionaries are just like regular dictionaries but have some extra capabilities relating to ordering operations. They have become less important now that the built-in [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") class gained the ability to remember insertion order (this new behavior became guaranteed in Python 3.7).
Some differences from [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") still remain:
- The regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") was designed to be very good at mapping operations. Tracking insertion order was secondary.
- The [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") was designed to be good at reordering operations. Space efficiency, iteration speed, and the performance of update operations were secondary.
- The [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") algorithm can handle frequent reordering operations better than [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict"). As shown in the recipes below, this makes it suitable for implementing various kinds of LRU caches.
- The equality operation for [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") checks for matching order.
A regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") can emulate the order sensitive equality test with `p == q and all(k1 == k2 for k1, k2 in zip(p, q))`.
- The [`popitem()`](https://docs.python.org/3/library/collections.html#collections.OrderedDict.popitem "collections.OrderedDict.popitem") method of [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") has a different signature. It accepts an optional argument to specify which item is popped.
A regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") can emulate OrderedDict’s `od.popitem(last=True)` with `d.popitem()` which is guaranteed to pop the rightmost (last) item.
A regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") can emulate OrderedDict’s `od.popitem(last=False)` with `(k := next(iter(d)), d.pop(k))` which will return and remove the leftmost (first) item if it exists.
- [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") has a [`move_to_end()`](https://docs.python.org/3/library/collections.html#collections.OrderedDict.move_to_end "collections.OrderedDict.move_to_end") method to efficiently reposition an element to an endpoint.
A regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") can emulate OrderedDict’s with `d[k] = d.pop(k)` which will move the key and its associated value to the rightmost (last) position.
A regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") does not have an efficient equivalent for OrderedDict’s `od.move_to_end(k, last=False)` which moves the key and its associated value to the leftmost (first) position.
- Until Python 3.8, [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") lacked a [`__reversed__()`](https://docs.python.org/3/reference/datamodel.html#object.__reversed__ "object.__reversed__") method.
*class* collections.OrderedDict(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.OrderedDict "Link to this definition")
*class* collections.OrderedDict(*mapping*, */*, *\*\*kwargs*)
*class* collections.OrderedDict(*iterable*, */*, *\*\*kwargs*)
Return an instance of a [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") subclass that has methods specialized for rearranging dictionary order.
Added in version 3.1.
popitem(*last\=True*)[¶](https://docs.python.org/3/library/collections.html#collections.OrderedDict.popitem "Link to this definition")
The `popitem()` method for ordered dictionaries returns and removes a (key, value) pair. The pairs are returned in LIFO order if *last* is true or FIFO order if false.
move\_to\_end(*key*, *last\=True*)[¶](https://docs.python.org/3/library/collections.html#collections.OrderedDict.move_to_end "Link to this definition")
Move an existing *key* to either end of an ordered dictionary. The item is moved to the right end if *last* is true (the default) or to the beginning if *last* is false. Raises [`KeyError`](https://docs.python.org/3/library/exceptions.html#KeyError "KeyError") if the *key* does not exist:
Copy
```
>>> d = OrderedDict.fromkeys('abcde')
>>> d.move_to_end('b')
>>> ''.join(d)
'acdeb'
>>> d.move_to_end('b', last=False)
>>> ''.join(d)
'bacde'
```
Added in version 3.2.
In addition to the usual mapping methods, ordered dictionaries also support reverse iteration using [`reversed()`](https://docs.python.org/3/library/functions.html#reversed "reversed").
Equality tests between [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") objects are order-sensitive and are roughly equivalent to `list(od1.items())==list(od2.items())`.
Equality tests between [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") objects and other [`Mapping`](https://docs.python.org/3/library/collections.abc.html#collections.abc.Mapping "collections.abc.Mapping") objects are order-insensitive like regular dictionaries. This allows `OrderedDict` objects to be substituted anywhere a regular dictionary is used.
Changed in version 3.5: The items, keys, and values [views](https://docs.python.org/3/glossary.html#term-dictionary-view) of [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") now support reverse iteration using [`reversed()`](https://docs.python.org/3/library/functions.html#reversed "reversed").
Changed in version 3.6: With the acceptance of [**PEP 468**](https://peps.python.org/pep-0468/), order is retained for keyword arguments passed to the [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") constructor and its [`update()`](https://docs.python.org/3/library/stdtypes.html#dict.update "dict.update") method.
Changed in version 3.9: Added merge (`|`) and update (`|=`) operators, specified in [**PEP 584**](https://peps.python.org/pep-0584/).
### [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") Examples and Recipes[¶](https://docs.python.org/3/library/collections.html#ordereddict-examples-and-recipes "Link to this heading")
It is straightforward to create an ordered dictionary variant that remembers the order the keys were *last* inserted. If a new entry overwrites an existing entry, the original insertion position is changed and moved to the end:
Copy
```
class LastUpdatedOrderedDict(OrderedDict):
'Store items in the order the keys were last added'
def __setitem__(self, key, value):
super().__setitem__(key, value)
self.move_to_end(key)
```
An [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") would also be useful for implementing variants of [`functools.lru_cache()`](https://docs.python.org/3/library/functools.html#functools.lru_cache "functools.lru_cache"):
Copy
```
from collections import OrderedDict
from time import time
class TimeBoundedLRU:
"LRU Cache that invalidates and refreshes old entries."
def __init__(self, func, maxsize=128, maxage=30):
self.cache = OrderedDict() # { args : (timestamp, result)}
self.func = func
self.maxsize = maxsize
self.maxage = maxage
def __call__(self, *args):
if args in self.cache:
self.cache.move_to_end(args)
timestamp, result = self.cache[args]
if time() - timestamp <= self.maxage:
return result
result = self.func(*args)
self.cache[args] = time(), result
if len(self.cache) > self.maxsize:
self.cache.popitem(last=False)
return result
```
Copy
```
class MultiHitLRUCache:
""" LRU cache that defers caching a result until
it has been requested multiple times.
To avoid flushing the LRU cache with one-time requests,
we don't cache until a request has been made more than once.
"""
def __init__(self, func, maxsize=128, maxrequests=4096, cache_after=1):
self.requests = OrderedDict() # { uncached_key : request_count }
self.cache = OrderedDict() # { cached_key : function_result }
self.func = func
self.maxrequests = maxrequests # max number of uncached requests
self.maxsize = maxsize # max number of stored return values
self.cache_after = cache_after
def __call__(self, *args):
if args in self.cache:
self.cache.move_to_end(args)
return self.cache[args]
result = self.func(*args)
self.requests[args] = self.requests.get(args, 0) + 1
if self.requests[args] <= self.cache_after:
self.requests.move_to_end(args)
if len(self.requests) > self.maxrequests:
self.requests.popitem(last=False)
else:
self.requests.pop(args, None)
self.cache[args] = result
if len(self.cache) > self.maxsize:
self.cache.popitem(last=False)
return result
```
## [`UserDict`](https://docs.python.org/3/library/collections.html#collections.UserDict "collections.UserDict") objects[¶](https://docs.python.org/3/library/collections.html#userdict-objects "Link to this heading")
The class, [`UserDict`](https://docs.python.org/3/library/collections.html#collections.UserDict "collections.UserDict") acts as a wrapper around dictionary objects. The need for this class has been partially supplanted by the ability to subclass directly from [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict"); however, this class can be easier to work with because the underlying dictionary is accessible as an attribute.
*class* collections.UserDict(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.UserDict "Link to this definition")
*class* collections.UserDict(*mapping*, */*, *\*\*kwargs*)
*class* collections.UserDict(*iterable*, */*, *\*\*kwargs*)
Class that simulates a dictionary. The instance’s contents are kept in a regular dictionary, which is accessible via the [`data`](https://docs.python.org/3/library/collections.html#collections.UserDict.data "collections.UserDict.data") attribute of `UserDict` instances. If arguments are provided, they are used to initialize `data`, like a regular dictionary.
In addition to supporting the methods and operations of mappings, `UserDict` instances provide the following attribute:
data[¶](https://docs.python.org/3/library/collections.html#collections.UserDict.data "Link to this definition")
A real dictionary used to store the contents of the `UserDict` class.
## [`UserList`](https://docs.python.org/3/library/collections.html#collections.UserList "collections.UserList") objects[¶](https://docs.python.org/3/library/collections.html#userlist-objects "Link to this heading")
This class acts as a wrapper around list objects. It is a useful base class for your own list-like classes which can inherit from them and override existing methods or add new ones. In this way, one can add new behaviors to lists.
The need for this class has been partially supplanted by the ability to subclass directly from [`list`](https://docs.python.org/3/library/stdtypes.html#list "list"); however, this class can be easier to work with because the underlying list is accessible as an attribute.
*class* collections.UserList(\[*list*\])[¶](https://docs.python.org/3/library/collections.html#collections.UserList "Link to this definition")
Class that simulates a list. The instance’s contents are kept in a regular list, which is accessible via the [`data`](https://docs.python.org/3/library/collections.html#collections.UserList.data "collections.UserList.data") attribute of `UserList` instances. The instance’s contents are initially set to a copy of *list*, defaulting to the empty list `[]`. *list* can be any iterable, for example a real Python list or a `UserList` object.
In addition to supporting the methods and operations of mutable sequences, `UserList` instances provide the following attribute:
data[¶](https://docs.python.org/3/library/collections.html#collections.UserList.data "Link to this definition")
A real [`list`](https://docs.python.org/3/library/stdtypes.html#list "list") object used to store the contents of the `UserList` class.
**Subclassing requirements:** Subclasses of [`UserList`](https://docs.python.org/3/library/collections.html#collections.UserList "collections.UserList") are expected to offer a constructor which can be called with either no arguments or one argument. List operations which return a new sequence attempt to create an instance of the actual implementation class. To do so, it assumes that the constructor can be called with a single parameter, which is a sequence object used as a data source.
If a derived class does not wish to comply with this requirement, all of the special methods supported by this class will need to be overridden; please consult the sources for information about the methods which need to be provided in that case.
## [`UserString`](https://docs.python.org/3/library/collections.html#collections.UserString "collections.UserString") objects[¶](https://docs.python.org/3/library/collections.html#userstring-objects "Link to this heading")
The class, [`UserString`](https://docs.python.org/3/library/collections.html#collections.UserString "collections.UserString") acts as a wrapper around string objects. The need for this class has been partially supplanted by the ability to subclass directly from [`str`](https://docs.python.org/3/library/stdtypes.html#str "str"); however, this class can be easier to work with because the underlying string is accessible as an attribute.
*class* collections.UserString(*seq*)[¶](https://docs.python.org/3/library/collections.html#collections.UserString "Link to this definition")
Class that simulates a string object. The instance’s content is kept in a regular string object, which is accessible via the [`data`](https://docs.python.org/3/library/collections.html#collections.UserString.data "collections.UserString.data") attribute of `UserString` instances. The instance’s contents are initially set to a copy of *seq*. The *seq* argument can be any object which can be converted into a string using the built-in [`str()`](https://docs.python.org/3/library/stdtypes.html#str "str") function.
In addition to supporting the methods and operations of strings, `UserString` instances provide the following attribute:
data[¶](https://docs.python.org/3/library/collections.html#collections.UserString.data "Link to this definition")
A real [`str`](https://docs.python.org/3/library/stdtypes.html#str "str") object used to store the contents of the `UserString` class.
Changed in version 3.5: New methods `__getnewargs__`, `__rmod__`, `casefold`, `format_map`, `isprintable`, and `maketrans`.
### [Table of Contents](https://docs.python.org/3/contents.html)
- [`collections` — Container datatypes](https://docs.python.org/3/library/collections.html)
- [`ChainMap` objects](https://docs.python.org/3/library/collections.html#chainmap-objects)
- [`ChainMap` Examples and Recipes](https://docs.python.org/3/library/collections.html#chainmap-examples-and-recipes)
- [`Counter` objects](https://docs.python.org/3/library/collections.html#counter-objects)
- [`deque` objects](https://docs.python.org/3/library/collections.html#deque-objects)
- [`deque` Recipes](https://docs.python.org/3/library/collections.html#deque-recipes)
- [`defaultdict` objects](https://docs.python.org/3/library/collections.html#defaultdict-objects)
- [`defaultdict` Examples](https://docs.python.org/3/library/collections.html#defaultdict-examples)
- [`namedtuple()` Factory Function for Tuples with Named Fields](https://docs.python.org/3/library/collections.html#namedtuple-factory-function-for-tuples-with-named-fields)
- [`OrderedDict` objects](https://docs.python.org/3/library/collections.html#ordereddict-objects)
- [`OrderedDict` Examples and Recipes](https://docs.python.org/3/library/collections.html#ordereddict-examples-and-recipes)
- [`UserDict` objects](https://docs.python.org/3/library/collections.html#userdict-objects)
- [`UserList` objects](https://docs.python.org/3/library/collections.html#userlist-objects)
- [`UserString` objects](https://docs.python.org/3/library/collections.html#userstring-objects)
#### Previous topic
[`calendar` — General calendar-related functions](https://docs.python.org/3/library/calendar.html "previous chapter")
#### Next topic
[`collections.abc` — Abstract Base Classes for Containers](https://docs.python.org/3/library/collections.abc.html "next chapter")
### This page
- [Report a bug](https://docs.python.org/3/bugs.html)
- [Improve this page](https://docs.python.org/3/improve-page.html?pagetitle=collections+%E2%80%94+Container+datatypes&pageurl=https%3A%2F%2Fdocs.python.org%2F3%2Flibrary%2Fcollections.html&pagesource=library%2Fcollections.rst)
- [Show source](https://github.com/python/cpython/blob/main/Doc/library/collections.rst?plain=1)
«
### Navigation
- [index](https://docs.python.org/3/genindex.html "General Index")
- [modules](https://docs.python.org/3/py-modindex.html "Python Module Index") \|
- [next](https://docs.python.org/3/library/collections.abc.html "collections.abc — Abstract Base Classes for Containers") \|
- [previous](https://docs.python.org/3/library/calendar.html "calendar — General calendar-related functions") \|
- 
- [Python](https://www.python.org/) »
- [3\.14.4 Documentation](https://docs.python.org/3/index.html) »
- [The Python Standard Library](https://docs.python.org/3/library/index.html) »
- [Data Types](https://docs.python.org/3/library/datatypes.html) »
- [`collections` — Container datatypes](https://docs.python.org/3/library/collections.html)
- \|
- Theme
\|
© [Copyright](https://docs.python.org/3/copyright.html) 2001 Python Software Foundation.
This page is licensed under the Python Software Foundation License Version 2.
Examples, recipes, and other code in the documentation are additionally licensed under the Zero Clause BSD License.
See [History and License](https://docs.python.org/license.html) for more information.
The Python Software Foundation is a non-profit corporation. [Please donate.](https://www.python.org/psf/donations/)
Last updated on Apr 09, 2026 (15:27 UTC). [Found a bug](https://docs.python.org/bugs.html)?
Created using [Sphinx](https://www.sphinx-doc.org/) 8.2.3. | |||||||||
| Readable Markdown | **Source code:** [Lib/collections/\_\_init\_\_.py](https://github.com/python/cpython/tree/3.14/Lib/collections/__init__.py)
***
This module implements specialized container datatypes providing alternatives to Python’s general purpose built-in containers, [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict"), [`list`](https://docs.python.org/3/library/stdtypes.html#list "list"), [`set`](https://docs.python.org/3/library/stdtypes.html#set "set"), and [`tuple`](https://docs.python.org/3/library/stdtypes.html#tuple "tuple").
| | |
|---|---|
| [`namedtuple()`](https://docs.python.org/3/library/collections.html#collections.namedtuple "collections.namedtuple") | factory function for creating tuple subclasses with named fields |
| [`deque`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque") | list-like container with fast appends and pops on either end |
| [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") | dict-like class for creating a single view of multiple mappings |
| [`Counter`](https://docs.python.org/3/library/collections.html#collections.Counter "collections.Counter") | dict subclass for counting [hashable](https://docs.python.org/3/glossary.html#term-hashable) objects |
| [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") | dict subclass that remembers the order entries were added |
| [`defaultdict`](https://docs.python.org/3/library/collections.html#collections.defaultdict "collections.defaultdict") | dict subclass that calls a factory function to supply missing values |
| [`UserDict`](https://docs.python.org/3/library/collections.html#collections.UserDict "collections.UserDict") | wrapper around dictionary objects for easier dict subclassing |
| [`UserList`](https://docs.python.org/3/library/collections.html#collections.UserList "collections.UserList") | wrapper around list objects for easier list subclassing |
| [`UserString`](https://docs.python.org/3/library/collections.html#collections.UserString "collections.UserString") | wrapper around string objects for easier string subclassing |
## [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") objects[¶](https://docs.python.org/3/library/collections.html#chainmap-objects "Link to this heading")
Added in version 3.3.
A [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") class is provided for quickly linking a number of mappings so they can be treated as a single unit. It is often much faster than creating a new dictionary and running multiple [`update()`](https://docs.python.org/3/library/stdtypes.html#dict.update "dict.update") calls.
The class can be used to simulate nested scopes and is useful in templating.
*class* collections.ChainMap(*\*maps*)[¶](https://docs.python.org/3/library/collections.html#collections.ChainMap "Link to this definition")
A `ChainMap` groups multiple dicts or other mappings together to create a single, updateable view. If no *maps* are specified, a single empty dictionary is provided so that a new chain always has at least one mapping.
The underlying mappings are stored in a list. That list is public and can be accessed or updated using the *maps* attribute. There is no other state.
Lookups search the underlying mappings successively until a key is found. In contrast, writes, updates, and deletions only operate on the first mapping.
A `ChainMap` incorporates the underlying mappings by reference. So, if one of the underlying mappings gets updated, those changes will be reflected in `ChainMap`.
All of the usual dictionary methods are supported. In addition, there is a *maps* attribute, a method for creating new subcontexts, and a property for accessing all but the first mapping:
maps[¶](https://docs.python.org/3/library/collections.html#collections.ChainMap.maps "Link to this definition")
A user updateable list of mappings. The list is ordered from first-searched to last-searched. It is the only stored state and can be modified to change which mappings are searched. The list should always contain at least one mapping.
new\_child(*m\=None*, *\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.ChainMap.new_child "Link to this definition")
Returns a new `ChainMap` containing a new map followed by all of the maps in the current instance. If `m` is specified, it becomes the new map at the front of the list of mappings; if not specified, an empty dict is used, so that a call to `d.new_child()` is equivalent to: `ChainMap({}, *d.maps)`. If any keyword arguments are specified, they update passed map or new empty dict. This method is used for creating subcontexts that can be updated without altering values in any of the parent mappings.
Changed in version 3.4: The optional `m` parameter was added.
Changed in version 3.10: Keyword arguments support was added.
parents[¶](https://docs.python.org/3/library/collections.html#collections.ChainMap.parents "Link to this definition")
Property returning a new `ChainMap` containing all of the maps in the current instance except the first one. This is useful for skipping the first map in the search. Use cases are similar to those for the [`nonlocal`](https://docs.python.org/3/reference/simple_stmts.html#nonlocal) keyword used in [nested scopes](https://docs.python.org/3/glossary.html#term-nested-scope). The use cases also parallel those for the built-in [`super()`](https://docs.python.org/3/library/functions.html#super "super") function. A reference to `d.parents` is equivalent to: `ChainMap(*d.maps[1:])`.
Note, the iteration order of a `ChainMap` is determined by scanning the mappings last to first:
```
>>> baseline = {'music': 'bach', 'art': 'rembrandt'}
>>> adjustments = {'art': 'van gogh', 'opera': 'carmen'}
>>> list(ChainMap(adjustments, baseline))
['music', 'art', 'opera']
```
This gives the same ordering as a series of [`dict.update()`](https://docs.python.org/3/library/stdtypes.html#dict.update "dict.update") calls starting with the last mapping:
```
>>> combined = baseline.copy()
>>> combined.update(adjustments)
>>> list(combined)
['music', 'art', 'opera']
```
Changed in version 3.9: Added support for `|` and `|=` operators, specified in [**PEP 584**](https://peps.python.org/pep-0584/).
See also
- The [MultiContext class](https://github.com/enthought/codetools/blob/4.0.0/codetools/contexts/multi_context.py) in the Enthought [CodeTools package](https://github.com/enthought/codetools) has options to support writing to any mapping in the chain.
- Django’s [Context class](https://github.com/django/django/blob/main/django/template/context.py) for templating is a read-only chain of mappings. It also features pushing and popping of contexts similar to the [`new_child()`](https://docs.python.org/3/library/collections.html#collections.ChainMap.new_child "collections.ChainMap.new_child") method and the [`parents`](https://docs.python.org/3/library/collections.html#collections.ChainMap.parents "collections.ChainMap.parents") property.
- The [Nested Contexts recipe](https://code.activestate.com/recipes/577434-nested-contexts-a-chain-of-mapping-objects/) has options to control whether writes and other mutations apply only to the first mapping or to any mapping in the chain.
- A [greatly simplified read-only version of Chainmap](https://code.activestate.com/recipes/305268/).
### [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") Examples and Recipes[¶](https://docs.python.org/3/library/collections.html#chainmap-examples-and-recipes "Link to this heading")
This section shows various approaches to working with chained maps.
Example of simulating Python’s internal lookup chain:
```
import builtins
pylookup = ChainMap(locals(), globals(), vars(builtins))
```
Example of letting user specified command-line arguments take precedence over environment variables which in turn take precedence over default values:
```
import os, argparse
defaults = {'color': 'red', 'user': 'guest'}
parser = argparse.ArgumentParser()
parser.add_argument('-u', '--user')
parser.add_argument('-c', '--color')
namespace = parser.parse_args()
command_line_args = {k: v for k, v in vars(namespace).items() if v is not None}
combined = ChainMap(command_line_args, os.environ, defaults)
print(combined['color'])
print(combined['user'])
```
Example patterns for using the [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") class to simulate nested contexts:
```
c = ChainMap() # Create root context
d = c.new_child() # Create nested child context
e = c.new_child() # Child of c, independent from d
e.maps[0] # Current context dictionary -- like Python's locals()
e.maps[-1] # Root context -- like Python's globals()
e.parents # Enclosing context chain -- like Python's nonlocals
d['x'] = 1 # Set value in current context
d['x'] # Get first key in the chain of contexts
del d['x'] # Delete from current context
list(d) # All nested values
k in d # Check all nested values
len(d) # Number of nested values
d.items() # All nested items
dict(d) # Flatten into a regular dictionary
```
The [`ChainMap`](https://docs.python.org/3/library/collections.html#collections.ChainMap "collections.ChainMap") class only makes updates (writes and deletions) to the first mapping in the chain while lookups will search the full chain. However, if deep writes and deletions are desired, it is easy to make a subclass that updates keys found deeper in the chain:
```
class DeepChainMap(ChainMap):
'Variant of ChainMap that allows direct updates to inner scopes'
def __setitem__(self, key, value):
for mapping in self.maps:
if key in mapping:
mapping[key] = value
return
self.maps[0][key] = value
def __delitem__(self, key):
for mapping in self.maps:
if key in mapping:
del mapping[key]
return
raise KeyError(key)
>>> d = DeepChainMap({'zebra': 'black'}, {'elephant': 'blue'}, {'lion': 'yellow'})
>>> d['lion'] = 'orange' # update an existing key two levels down
>>> d['snake'] = 'red' # new keys get added to the topmost dict
>>> del d['elephant'] # remove an existing key one level down
>>> d # display result
DeepChainMap({'zebra': 'black', 'snake': 'red'}, {}, {'lion': 'orange'})
```
## [`Counter`](https://docs.python.org/3/library/collections.html#collections.Counter "collections.Counter") objects[¶](https://docs.python.org/3/library/collections.html#counter-objects "Link to this heading")
A counter tool is provided to support convenient and rapid tallies. For example:
```
>>> # Tally occurrences of words in a list
>>> cnt = Counter()
>>> for word in ['red', 'blue', 'red', 'green', 'blue', 'blue']:
... cnt[word] += 1
...
>>> cnt
Counter({'blue': 3, 'red': 2, 'green': 1})
>>> # Find the ten most common words in Hamlet
>>> import re
>>> words = re.findall(r'\w+', open('hamlet.txt').read().lower())
>>> Counter(words).most_common(10)
[('the', 1143), ('and', 966), ('to', 762), ('of', 669), ('i', 631),
('you', 554), ('a', 546), ('my', 514), ('hamlet', 471), ('in', 451)]
```
*class* collections.Counter(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.Counter "Link to this definition")
*class* collections.Counter(*iterable*, */*, *\*\*kwargs*)
*class* collections.Counter(*mapping*, */*, *\*\*kwargs*)
A `Counter` is a [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") subclass for counting [hashable](https://docs.python.org/3/glossary.html#term-hashable) objects. It is a collection where elements are stored as dictionary keys and their counts are stored as dictionary values. Counts are allowed to be any integer value including zero or negative counts. The `Counter` class is similar to bags or multisets in other languages.
Elements are counted from an *iterable* or initialized from another *mapping* (or counter):
```
>>> c = Counter() # a new, empty counter
>>> c = Counter('gallahad') # a new counter from an iterable
>>> c = Counter({'red': 4, 'blue': 2}) # a new counter from a mapping
>>> c = Counter(cats=4, dogs=8) # a new counter from keyword args
```
Counter objects have a dictionary interface except that they return a zero count for missing items instead of raising a [`KeyError`](https://docs.python.org/3/library/exceptions.html#KeyError "KeyError"):
```
>>> c = Counter(['eggs', 'ham'])
>>> c['bacon'] # count of a missing element is zero
0
```
Setting a count to zero does not remove an element from a counter. Use `del` to remove it entirely:
```
>>> c['sausage'] = 0 # counter entry with a zero count
>>> del c['sausage'] # del actually removes the entry
```
Added in version 3.1.
Changed in version 3.7: As a [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") subclass, `Counter` inherited the capability to remember insertion order. Math operations on *Counter* objects also preserve order. Results are ordered according to when an element is first encountered in the left operand and then by the order encountered in the right operand.
Counter objects support additional methods beyond those available for all dictionaries:
elements()[¶](https://docs.python.org/3/library/collections.html#collections.Counter.elements "Link to this definition")
Return an iterator over elements repeating each as many times as its count. Elements are returned in the order first encountered. If an element’s count is less than one, `elements()` will ignore it.
```
>>> c = Counter(a=4, b=2, c=0, d=-2)
>>> sorted(c.elements())
['a', 'a', 'a', 'a', 'b', 'b']
```
most\_common(*n\=None*)[¶](https://docs.python.org/3/library/collections.html#collections.Counter.most_common "Link to this definition")
Return a list of the *n* most common elements and their counts from the most common to the least. If *n* is omitted or `None`, `most_common()` returns *all* elements in the counter. Elements with equal counts are ordered in the order first encountered:
```
>>> Counter('abracadabra').most_common(3)
[('a', 5), ('b', 2), ('r', 2)]
```
subtract(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.Counter.subtract "Link to this definition")
subtract(*iterable*, */*, *\*\*kwargs*)
subtract(*mapping*, */*, *\*\*kwargs*)
Elements are subtracted from an *iterable* or from another *mapping* (or counter). Like [`dict.update()`](https://docs.python.org/3/library/stdtypes.html#dict.update "dict.update") but subtracts counts instead of replacing them. Both inputs and outputs may be zero or negative.
```
>>> c = Counter(a=4, b=2, c=0, d=-2)
>>> d = Counter(a=1, b=2, c=3, d=4)
>>> c.subtract(d)
>>> c
Counter({'a': 3, 'b': 0, 'c': -3, 'd': -6})
```
Added in version 3.2.
total()[¶](https://docs.python.org/3/library/collections.html#collections.Counter.total "Link to this definition")
Compute the sum of the counts.
```
>>> c = Counter(a=10, b=5, c=0)
>>> c.total()
15
```
Added in version 3.10.
The usual dictionary methods are available for `Counter` objects except for two which work differently for counters.
fromkeys(*iterable*)[¶](https://docs.python.org/3/library/collections.html#collections.Counter.fromkeys "Link to this definition")
This class method is not implemented for `Counter` objects.
update(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.Counter.update "Link to this definition")
update(*iterable*, */*, *\*\*kwargs*)
update(*mapping*, */*, *\*\*kwargs*)
Elements are counted from an *iterable* or added-in from another *mapping* (or counter). Like [`dict.update()`](https://docs.python.org/3/library/stdtypes.html#dict.update "dict.update") but adds counts instead of replacing them. Also, the *iterable* is expected to be a sequence of elements, not a sequence of `(key, value)` pairs.
Counters support rich comparison operators for equality, subset, and superset relationships: `==`, `!=`, `<`, `<=`, `>`, `>=`. All of those tests treat missing elements as having zero counts so that `Counter(a=1) == Counter(a=1, b=0)` returns true.
Changed in version 3.10: Rich comparison operations were added.
Changed in version 3.10: In equality tests, missing elements are treated as having zero counts. Formerly, `Counter(a=3)` and `Counter(a=3, b=0)` were considered distinct.
Common patterns for working with [`Counter`](https://docs.python.org/3/library/collections.html#collections.Counter "collections.Counter") objects:
```
c.total() # total of all counts
c.clear() # reset all counts
list(c) # list unique elements
set(c) # convert to a set
dict(c) # convert to a regular dictionary
c.items() # access the (elem, cnt) pairs
Counter(dict(list_of_pairs)) # convert from a list of (elem, cnt) pairs
c.most_common()[:-n-1:-1] # n least common elements
+c # remove zero and negative counts
```
Several mathematical operations are provided for combining [`Counter`](https://docs.python.org/3/library/collections.html#collections.Counter "collections.Counter") objects to produce multisets (counters that have counts greater than zero). Addition and subtraction combine counters by adding or subtracting the counts of corresponding elements. Intersection and union return the minimum and maximum of corresponding counts. Equality and inclusion compare corresponding counts. Each operation can accept inputs with signed counts, but the output will exclude results with counts of zero or less.
```
>>> c = Counter(a=3, b=1)
>>> d = Counter(a=1, b=2)
>>> c + d # add two counters together: c[x] + d[x]
Counter({'a': 4, 'b': 3})
>>> c - d # subtract (keeping only positive counts)
Counter({'a': 2})
>>> c & d # intersection: min(c[x], d[x])
Counter({'a': 1, 'b': 1})
>>> c | d # union: max(c[x], d[x])
Counter({'a': 3, 'b': 2})
>>> c == d # equality: c[x] == d[x]
False
>>> c <= d # inclusion: c[x] <= d[x]
False
```
Unary addition and subtraction are shortcuts for adding an empty counter or subtracting from an empty counter.
```
>>> c = Counter(a=2, b=-4)
>>> +c
Counter({'a': 2})
>>> -c
Counter({'b': 4})
```
Added in version 3.3: Added support for unary plus, unary minus, and in-place multiset operations.
Note
Counters were primarily designed to work with positive integers to represent running counts; however, care was taken to not unnecessarily preclude use cases needing other types or negative values. To help with those use cases, this section documents the minimum range and type restrictions.
- The [`Counter`](https://docs.python.org/3/library/collections.html#collections.Counter "collections.Counter") class itself is a dictionary subclass with no restrictions on its keys and values. The values are intended to be numbers representing counts, but you *could* store anything in the value field.
- The [`most_common()`](https://docs.python.org/3/library/collections.html#collections.Counter.most_common "collections.Counter.most_common") method requires only that the values be orderable.
- For in-place operations such as `c[key] += 1`, the value type need only support addition and subtraction. So fractions, floats, and decimals would work and negative values are supported. The same is also true for [`update()`](https://docs.python.org/3/library/collections.html#collections.Counter.update "collections.Counter.update") and [`subtract()`](https://docs.python.org/3/library/collections.html#collections.Counter.subtract "collections.Counter.subtract") which allow negative and zero values for both inputs and outputs.
- The multiset methods are designed only for use cases with positive values. The inputs may be negative or zero, but only outputs with positive values are created. There are no type restrictions, but the value type needs to support addition, subtraction, and comparison.
- The [`elements()`](https://docs.python.org/3/library/collections.html#collections.Counter.elements "collections.Counter.elements") method requires integer counts. It ignores zero and negative counts.
See also
- [Bag class](https://www.gnu.org/software/smalltalk/manual-base/html_node/Bag.html) in Smalltalk.
- Wikipedia entry for [Multisets](https://en.wikipedia.org/wiki/Multiset).
- [C++ multisets](http://www.java2s.com/Tutorial/Cpp/0380__set-multiset/Catalog0380__set-multiset.htm) tutorial with examples.
- For mathematical operations on multisets and their use cases, see *Knuth, Donald. The Art of Computer Programming Volume II, Section 4.6.3, Exercise 19*.
- To enumerate all distinct multisets of a given size over a given set of elements, see [`itertools.combinations_with_replacement()`](https://docs.python.org/3/library/itertools.html#itertools.combinations_with_replacement "itertools.combinations_with_replacement"):
```
map(Counter, combinations_with_replacement('ABC', 2)) # --> AA AB AC BB BC CC
```
## [`deque`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque") objects[¶](https://docs.python.org/3/library/collections.html#deque-objects "Link to this heading")
*class* collections.deque(\[*iterable*\[, *maxlen*\]\])[¶](https://docs.python.org/3/library/collections.html#collections.deque "Link to this definition")
Returns a new deque object initialized left-to-right (using [`append()`](https://docs.python.org/3/library/collections.html#collections.deque.append "collections.deque.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 [`list`](https://docs.python.org/3/library/stdtypes.html#list "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.
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.
Deque objects support the following methods:
append(*item*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.append "Link to this definition")
Add *item* to the right side of the deque.
appendleft(*item*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.appendleft "Link to this definition")
Add *item* to the left side of the deque.
clear()[¶](https://docs.python.org/3/library/collections.html#collections.deque.clear "Link to this definition")
Remove all elements from the deque leaving it with length 0.
copy()[¶](https://docs.python.org/3/library/collections.html#collections.deque.copy "Link to this definition")
Create a shallow copy of the deque.
Added in version 3.5.
count(*value*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.count "Link to this definition")
Count the number of deque elements equal to *value*.
Added in version 3.2.
extend(*iterable*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.extend "Link to this definition")
Extend the right side of the deque by appending elements from the iterable argument.
extendleft(*iterable*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.extendleft "Link to this definition")
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.
index(*value*\[, *start*\[, *stop*\]\])[¶](https://docs.python.org/3/library/collections.html#collections.deque.index "Link to this definition")
Return the position of *value* in the deque (at or after index *start* and before index *stop*). Returns the first match or raises [`ValueError`](https://docs.python.org/3/library/exceptions.html#ValueError "ValueError") if not found.
Added in version 3.5.
insert(*index*, *value*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.insert "Link to this definition")
Insert *value* into the deque at position *index*.
If the insertion would cause a bounded deque to grow beyond *maxlen*, an [`IndexError`](https://docs.python.org/3/library/exceptions.html#IndexError "IndexError") is raised.
Added in version 3.5.
pop()[¶](https://docs.python.org/3/library/collections.html#collections.deque.pop "Link to this definition")
Remove and return an element from the right side of the deque. If no elements are present, raises an [`IndexError`](https://docs.python.org/3/library/exceptions.html#IndexError "IndexError").
popleft()[¶](https://docs.python.org/3/library/collections.html#collections.deque.popleft "Link to this definition")
Remove and return an element from the left side of the deque. If no elements are present, raises an [`IndexError`](https://docs.python.org/3/library/exceptions.html#IndexError "IndexError").
remove(*value*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.remove "Link to this definition")
Remove the first occurrence of *value*. If not found, raises a [`ValueError`](https://docs.python.org/3/library/exceptions.html#ValueError "ValueError").
reverse()[¶](https://docs.python.org/3/library/collections.html#collections.deque.reverse "Link to this definition")
Reverse the elements of the deque in-place and then return `None`.
Added in version 3.2.
rotate(*n\=1*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.deque.rotate "Link to this definition")
Rotate the deque *n* steps to the right. If *n* is negative, rotate to the left.
When the deque is not empty, rotating one step to the right is equivalent to `d.appendleft(d.pop())`, and rotating one step to the left is equivalent to `d.append(d.popleft())`.
Deque objects also provide one read-only attribute:
maxlen[¶](https://docs.python.org/3/library/collections.html#collections.deque.maxlen "Link to this definition")
Maximum size of a deque or `None` if unbounded.
Added in version 3.1.
In addition to the above, deques support iteration, pickling, `len(d)`, `reversed(d)`, `copy.copy(d)`, `copy.deepcopy(d)`, membership testing with the [`in`](https://docs.python.org/3/reference/expressions.html#in) operator, and subscript references such as `d[0]` to access the first element. Indexed access is *O*(1) at both ends but slows to *O*(*n*) in the middle. For fast random access, use lists instead.
Starting in version 3.5, deques support `__add__()`, `__mul__()`, and `__imul__()`.
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`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque") Recipes[¶](https://docs.python.org/3/library/collections.html#deque-recipes "Link to this heading")
This section shows various approaches to working with deques.
Bounded length deques provide functionality similar to the `tail` filter in Unix:
```
def tail(filename, n=10):
'Return the last n lines of a file'
with open(filename) as f:
return deque(f, n)
```
Another approach to using deques is to maintain a sequence of recently added elements by appending to the right and popping to the left:
```
def moving_average(iterable, n=3):
# moving_average([40, 30, 50, 46, 39, 44]) --> 40.0 42.0 45.0 43.0
# https://en.wikipedia.org/wiki/Moving_average
it = iter(iterable)
d = deque(itertools.islice(it, n-1))
d.appendleft(0)
s = sum(d)
for elem in it:
s += elem - d.popleft()
d.append(elem)
yield s / n
```
A [round-robin scheduler](https://en.wikipedia.org/wiki/Round-robin_scheduling) can be implemented with input iterators stored in a [`deque`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque"). Values are yielded from the active iterator in position zero. If that iterator is exhausted, it can be removed with [`popleft()`](https://docs.python.org/3/library/collections.html#collections.deque.popleft "collections.deque.popleft"); otherwise, it can be cycled back to the end with the [`rotate()`](https://docs.python.org/3/library/collections.html#collections.deque.rotate "collections.deque.rotate") method:
```
def roundrobin(*iterables):
"roundrobin('ABC', 'D', 'EF') --> A D E B F C"
iterators = deque(map(iter, iterables))
while iterators:
try:
while True:
yield next(iterators[0])
iterators.rotate(-1)
except StopIteration:
# Remove an exhausted iterator.
iterators.popleft()
```
The [`rotate()`](https://docs.python.org/3/library/collections.html#collections.deque.rotate "collections.deque.rotate") method provides a way to implement [`deque`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque") slicing and deletion. For example, a pure Python implementation of `del d[n]` relies on the `rotate()` method to position elements to be popped:
```
def delete_nth(d, n):
d.rotate(-n)
d.popleft()
d.rotate(n)
```
To implement [`deque`](https://docs.python.org/3/library/collections.html#collections.deque "collections.deque") slicing, use a similar approach applying [`rotate()`](https://docs.python.org/3/library/collections.html#collections.deque.rotate "collections.deque.rotate") to bring a target element to the left side of the deque. Remove old entries with [`popleft()`](https://docs.python.org/3/library/collections.html#collections.deque.popleft "collections.deque.popleft"), add new entries with [`extend()`](https://docs.python.org/3/library/collections.html#collections.deque.extend "collections.deque.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`.
## [`defaultdict`](https://docs.python.org/3/library/collections.html#collections.defaultdict "collections.defaultdict") objects[¶](https://docs.python.org/3/library/collections.html#defaultdict-objects "Link to this heading")
*class* collections.defaultdict(*default\_factory\=None*, */*, *\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.defaultdict "Link to this definition")
*class* collections.defaultdict(*default\_factory*, *mapping*, */*, *\*\*kwargs*)
*class* collections.defaultdict(*default\_factory*, *iterable*, */*, *\*\*kwargs*)
Return a new dictionary-like object. `defaultdict` is a subclass of the built-in [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") class. It overrides one method and adds one writable instance variable. The remaining functionality is the same as for the `dict` class and is not documented here.
The first argument provides the initial value for the [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") attribute; it defaults to `None`. All remaining arguments are treated the same as if they were passed to the [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") constructor, including keyword arguments.
`defaultdict` objects support the following method in addition to the standard [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") operations:
\_\_missing\_\_(*key*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.defaultdict.__missing__ "Link to this definition")
If the [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") attribute is `None`, this raises a [`KeyError`](https://docs.python.org/3/library/exceptions.html#KeyError "KeyError") exception with the *key* as argument.
If [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.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 [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") raises an exception this exception is propagated unchanged.
This method is called by the [`__getitem__()`](https://docs.python.org/3/reference/datamodel.html#object.__getitem__ "object.__getitem__") method of the [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") class when the requested key is not found; whatever it returns or raises is then returned or raised by `__getitem__()`.
Note that `__missing__()` is *not* called for any operations besides [`__getitem__()`](https://docs.python.org/3/reference/datamodel.html#object.__getitem__ "object.__getitem__"). This means that [`get()`](https://docs.python.org/3/library/stdtypes.html#dict.get "dict.get") will, like normal dictionaries, return `None` as a default rather than using [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory").
`defaultdict` objects support the following instance variable:
default\_factory[¶](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "Link to this definition")
This attribute is used by the [`__missing__()`](https://docs.python.org/3/library/collections.html#collections.defaultdict.__missing__ "collections.defaultdict.__missing__") method; it is initialized from the first argument to the constructor, if present, or to `None`, if absent.
Changed in version 3.9: Added merge (`|`) and update (`|=`) operators, specified in [**PEP 584**](https://peps.python.org/pep-0584/).
### [`defaultdict`](https://docs.python.org/3/library/collections.html#collections.defaultdict "collections.defaultdict") Examples[¶](https://docs.python.org/3/library/collections.html#defaultdict-examples "Link to this heading")
Using [`list`](https://docs.python.org/3/library/stdtypes.html#list "list") as the [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.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)
...
>>> sorted(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 [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") function which returns an empty [`list`](https://docs.python.org/3/library/stdtypes.html#list "list"). The [`list.append()`](https://docs.python.org/3/library/stdtypes.html#list.append "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 `list.append()` operation adds another value to the list. This technique is simpler and faster than an equivalent technique using [`dict.setdefault()`](https://docs.python.org/3/library/stdtypes.html#dict.setdefault "dict.setdefault"):
```
>>> d = {}
>>> for k, v in s:
... d.setdefault(k, []).append(v)
...
>>> sorted(d.items())
[('blue', [2, 4]), ('red', [1]), ('yellow', [1, 3])]
```
Setting the [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") to [`int`](https://docs.python.org/3/library/functions.html#int "int") makes the [`defaultdict`](https://docs.python.org/3/library/collections.html#collections.defaultdict "collections.defaultdict") useful for counting (like a bag or multiset in other languages):
```
>>> s = 'mississippi'
>>> d = defaultdict(int)
>>> for k in s:
... d[k] += 1
...
>>> sorted(d.items())
[('i', 4), ('m', 1), ('p', 2), ('s', 4)]
```
When a letter is first encountered, it is missing from the mapping, so the [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") function calls [`int()`](https://docs.python.org/3/library/functions.html#int "int") to supply a default count of zero. The increment operation then builds up the count for each letter.
The function [`int()`](https://docs.python.org/3/library/functions.html#int "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 a lambda function which can supply any constant value (not just zero):
```
>>> def constant_factory(value):
... return lambda: value
...
>>> 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 [`default_factory`](https://docs.python.org/3/library/collections.html#collections.defaultdict.default_factory "collections.defaultdict.default_factory") to [`set`](https://docs.python.org/3/library/stdtypes.html#set "set") makes the [`defaultdict`](https://docs.python.org/3/library/collections.html#collections.defaultdict "collections.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)
...
>>> sorted(d.items())
[('blue', {2, 4}), ('red', {1, 3})]
```
## [`namedtuple()`](https://docs.python.org/3/library/collections.html#collections.namedtuple "collections.namedtuple") Factory Function for Tuples with Named Fields[¶](https://docs.python.org/3/library/collections.html#namedtuple-factory-function-for-tuples-with-named-fields "Link to this heading")
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.
collections.namedtuple(*typename*, *field\_names*, *\**, *rename\=False*, *defaults\=None*, *module\=None*)[¶](https://docs.python.org/3/library/collections.html#collections.namedtuple "Link to this definition")
Returns a new tuple subclass named *typename*. The new subclass is used to create tuple-like objects that have fields accessible by attribute lookup as well as being indexable and iterable. Instances of the subclass also have a helpful docstring (with *typename* and *field\_names*) and a helpful [`__repr__()`](https://docs.python.org/3/reference/datamodel.html#object.__repr__ "object.__repr__") method which lists the tuple contents in a `name=value` format.
The *field\_names* are a sequence of strings such as `['x', 'y']`. Alternatively, *field\_names* can be a single string with each fieldname separated by whitespace and/or commas, for example `'x y'` or `'x, y'`.
Any valid Python identifier may be used for a fieldname except for names starting with an underscore. Valid identifiers consist of letters, digits, and underscores but do not start with a digit or underscore and cannot be a [`keyword`](https://docs.python.org/3/library/keyword.html#module-keyword "keyword: Test whether a string is a keyword in Python.") such as *class*, *for*, *return*, *global*, *pass*, or *raise*.
If *rename* is true, invalid fieldnames are automatically replaced with positional names. For example, `['abc', 'def', 'ghi', 'abc']` is converted to `['abc', '_1', 'ghi', '_3']`, eliminating the keyword `def` and the duplicate fieldname `abc`.
*defaults* can be `None` or an [iterable](https://docs.python.org/3/glossary.html#term-iterable) of default values. Since fields with a default value must come after any fields without a default, the *defaults* are applied to the rightmost parameters. For example, if the fieldnames are `['x', 'y', 'z']` and the defaults are `(1, 2)`, then `x` will be a required argument, `y` will default to `1`, and `z` will default to `2`.
If *module* is defined, the [`__module__`](https://docs.python.org/3/reference/datamodel.html#type.__module__ "type.__module__") attribute of the named tuple is set to that value.
Named tuple instances do not have per-instance dictionaries, so they are lightweight and require no more memory than regular tuples.
To support pickling, the named tuple class should be assigned to a variable that matches *typename*.
Changed in version 3.1: Added support for *rename*.
Changed in version 3.6: Added the *module* parameter.
Changed in version 3.7: Removed the *verbose* parameter and the `_source` attribute.
Changed in version 3.7: Added the *defaults* parameter and the [`_field_defaults`](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._field_defaults "collections.somenamedtuple._field_defaults") attribute.
```
>>> # Basic example
>>> Point = namedtuple('Point', ['x', 'y'])
>>> p = Point(11, y=22) # instantiate with positional or keyword arguments
>>> p[0] + p[1] # indexable like the plain tuple (11, 22)
33
>>> x, y = p # unpack like a regular tuple
>>> x, y
(11, 22)
>>> p.x + p.y # fields also accessible 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 [`csv`](https://docs.python.org/3/library/csv.html#module-csv "csv: Write and read tabular data to and from delimited files.") or [`sqlite3`](https://docs.python.org/3/library/sqlite3.html#module-sqlite3 "sqlite3: A DB-API 2.0 implementation using SQLite 3.x.") modules:
```
EmployeeRecord = namedtuple('EmployeeRecord', 'name, age, title, department, paygrade')
import csv
for emp in map(EmployeeRecord._make, csv.reader(open("employees.csv", "rb"))):
print(emp.name, emp.title)
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()):
print(emp.name, emp.title)
```
In addition to the methods inherited from tuples, named tuples support three additional methods and two attributes. To prevent conflicts with field names, the method and attribute names start with an underscore.
*classmethod* somenamedtuple.\_make(*iterable*, */*)[¶](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._make "Link to this definition")
Class method that makes a new instance from an existing sequence or iterable.
```
>>> t = [11, 22]
>>> Point._make(t)
Point(x=11, y=22)
```
somenamedtuple.\_asdict()[¶](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._asdict "Link to this definition")
Return a new [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") which maps field names to their corresponding values:
```
>>> p = Point(x=11, y=22)
>>> p._asdict()
{'x': 11, 'y': 22}
```
Changed in version 3.1: Returns an [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") instead of a regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict").
Changed in version 3.8: Returns a regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") instead of an [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict"). As of Python 3.7, regular dicts are guaranteed to be ordered. If the extra features of `OrderedDict` are required, the suggested remediation is to cast the result to the desired type: `OrderedDict(nt._asdict())`.
somenamedtuple.\_replace(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._replace "Link to this definition")
Return a new instance of the named tuple replacing specified fields with new values:
```
>>> p = Point(x=11, y=22)
>>> p._replace(x=33)
Point(x=33, y=22)
>>> for partnum, record in inventory.items():
... inventory[partnum] = record._replace(price=newprices[partnum], timestamp=time.now())
```
Named tuples are also supported by generic function [`copy.replace()`](https://docs.python.org/3/library/copy.html#copy.replace "copy.replace").
Changed in version 3.13: Raise [`TypeError`](https://docs.python.org/3/library/exceptions.html#TypeError "TypeError") instead of [`ValueError`](https://docs.python.org/3/library/exceptions.html#ValueError "ValueError") for invalid keyword arguments.
somenamedtuple.\_fields[¶](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._fields "Link to this definition")
Tuple of strings listing the field names. Useful for introspection and for creating new named tuple types from existing named tuples.
```
>>> p._fields # view the field names
('x', 'y')
>>> Color = namedtuple('Color', 'red green blue')
>>> Pixel = namedtuple('Pixel', Point._fields + Color._fields)
>>> Pixel(11, 22, 128, 255, 0)
Pixel(x=11, y=22, red=128, green=255, blue=0)
```
somenamedtuple.\_field\_defaults[¶](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._field_defaults "Link to this definition")
Dictionary mapping field names to default values.
```
>>> Account = namedtuple('Account', ['type', 'balance'], defaults=[0])
>>> Account._field_defaults
{'balance': 0}
>>> Account('premium')
Account(type='premium', balance=0)
```
To retrieve a field whose name is stored in a string, use the [`getattr()`](https://docs.python.org/3/library/functions.html#getattr "getattr") function:
```
>>> getattr(p, 'x')
11
```
To convert a dictionary to a named tuple, use the double-star-operator (as described in [Unpacking Argument Lists](https://docs.python.org/3/tutorial/controlflow.html#tut-unpacking-arguments)):
```
>>> 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 fixed-width print format:
```
>>> class Point(namedtuple('Point', ['x', 'y'])):
... __slots__ = ()
... @property
... def hypot(self):
... return (self.x ** 2 + self.y ** 2) ** 0.5
... def __str__(self):
... return 'Point: x=%6.3f y=%6.3f hypot=%6.3f' % (self.x, self.y, self.hypot)
>>> for p in Point(3, 4), Point(14, 5/7):
... print(p)
Point: x= 3.000 y= 4.000 hypot= 5.000
Point: x=14.000 y= 0.714 hypot=14.018
```
The subclass shown above sets `__slots__` to an empty tuple. This helps keep memory requirements low by preventing the creation of instance dictionaries.
Subclassing is not useful for adding new, stored fields. Instead, simply create a new named tuple type from the [`_fields`](https://docs.python.org/3/library/collections.html#collections.somenamedtuple._fields "collections.somenamedtuple._fields") attribute:
```
>>> Point3D = namedtuple('Point3D', Point._fields + ('z',))
```
Docstrings can be customized by making direct assignments to the `__doc__` fields:
```
>>> Book = namedtuple('Book', ['id', 'title', 'authors'])
>>> Book.__doc__ += ': Hardcover book in active collection'
>>> Book.id.__doc__ = '13-digit ISBN'
>>> Book.title.__doc__ = 'Title of first printing'
>>> Book.authors.__doc__ = 'List of authors sorted by last name'
```
Changed in version 3.5: Property docstrings became writeable.
See also
- See [`typing.NamedTuple`](https://docs.python.org/3/library/typing.html#typing.NamedTuple "typing.NamedTuple") for a way to add type hints for named tuples. It also provides an elegant notation using the [`class`](https://docs.python.org/3/reference/compound_stmts.html#class) keyword:
```
class Component(NamedTuple):
part_number: int
weight: float
description: Optional[str] = None
```
- See [`types.SimpleNamespace()`](https://docs.python.org/3/library/types.html#types.SimpleNamespace "types.SimpleNamespace") for a mutable namespace based on an underlying dictionary instead of a tuple.
- The [`dataclasses`](https://docs.python.org/3/library/dataclasses.html#module-dataclasses "dataclasses: Generate special methods on user-defined classes.") module provides a decorator and functions for automatically adding generated special methods to user-defined classes.
## [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") objects[¶](https://docs.python.org/3/library/collections.html#ordereddict-objects "Link to this heading")
Ordered dictionaries are just like regular dictionaries but have some extra capabilities relating to ordering operations. They have become less important now that the built-in [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") class gained the ability to remember insertion order (this new behavior became guaranteed in Python 3.7).
Some differences from [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") still remain:
- The regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") was designed to be very good at mapping operations. Tracking insertion order was secondary.
- The [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") was designed to be good at reordering operations. Space efficiency, iteration speed, and the performance of update operations were secondary.
- The [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") algorithm can handle frequent reordering operations better than [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict"). As shown in the recipes below, this makes it suitable for implementing various kinds of LRU caches.
- The equality operation for [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") checks for matching order.
A regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") can emulate the order sensitive equality test with `p == q and all(k1 == k2 for k1, k2 in zip(p, q))`.
- The [`popitem()`](https://docs.python.org/3/library/collections.html#collections.OrderedDict.popitem "collections.OrderedDict.popitem") method of [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") has a different signature. It accepts an optional argument to specify which item is popped.
A regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") can emulate OrderedDict’s `od.popitem(last=True)` with `d.popitem()` which is guaranteed to pop the rightmost (last) item.
A regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") can emulate OrderedDict’s `od.popitem(last=False)` with `(k := next(iter(d)), d.pop(k))` which will return and remove the leftmost (first) item if it exists.
- [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") has a [`move_to_end()`](https://docs.python.org/3/library/collections.html#collections.OrderedDict.move_to_end "collections.OrderedDict.move_to_end") method to efficiently reposition an element to an endpoint.
A regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") can emulate OrderedDict’s with `d[k] = d.pop(k)` which will move the key and its associated value to the rightmost (last) position.
A regular [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") does not have an efficient equivalent for OrderedDict’s `od.move_to_end(k, last=False)` which moves the key and its associated value to the leftmost (first) position.
- Until Python 3.8, [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") lacked a [`__reversed__()`](https://docs.python.org/3/reference/datamodel.html#object.__reversed__ "object.__reversed__") method.
*class* collections.OrderedDict(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.OrderedDict "Link to this definition")
*class* collections.OrderedDict(*mapping*, */*, *\*\*kwargs*)
*class* collections.OrderedDict(*iterable*, */*, *\*\*kwargs*)
Return an instance of a [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict") subclass that has methods specialized for rearranging dictionary order.
Added in version 3.1.
popitem(*last\=True*)[¶](https://docs.python.org/3/library/collections.html#collections.OrderedDict.popitem "Link to this definition")
The `popitem()` method for ordered dictionaries returns and removes a (key, value) pair. The pairs are returned in LIFO order if *last* is true or FIFO order if false.
move\_to\_end(*key*, *last\=True*)[¶](https://docs.python.org/3/library/collections.html#collections.OrderedDict.move_to_end "Link to this definition")
Move an existing *key* to either end of an ordered dictionary. The item is moved to the right end if *last* is true (the default) or to the beginning if *last* is false. Raises [`KeyError`](https://docs.python.org/3/library/exceptions.html#KeyError "KeyError") if the *key* does not exist:
```
>>> d = OrderedDict.fromkeys('abcde')
>>> d.move_to_end('b')
>>> ''.join(d)
'acdeb'
>>> d.move_to_end('b', last=False)
>>> ''.join(d)
'bacde'
```
Added in version 3.2.
In addition to the usual mapping methods, ordered dictionaries also support reverse iteration using [`reversed()`](https://docs.python.org/3/library/functions.html#reversed "reversed").
Equality tests between [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") objects are order-sensitive and are roughly equivalent to `list(od1.items())==list(od2.items())`.
Equality tests between [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") objects and other [`Mapping`](https://docs.python.org/3/library/collections.abc.html#collections.abc.Mapping "collections.abc.Mapping") objects are order-insensitive like regular dictionaries. This allows `OrderedDict` objects to be substituted anywhere a regular dictionary is used.
Changed in version 3.5: The items, keys, and values [views](https://docs.python.org/3/glossary.html#term-dictionary-view) of [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") now support reverse iteration using [`reversed()`](https://docs.python.org/3/library/functions.html#reversed "reversed").
Changed in version 3.6: With the acceptance of [**PEP 468**](https://peps.python.org/pep-0468/), order is retained for keyword arguments passed to the [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") constructor and its [`update()`](https://docs.python.org/3/library/stdtypes.html#dict.update "dict.update") method.
Changed in version 3.9: Added merge (`|`) and update (`|=`) operators, specified in [**PEP 584**](https://peps.python.org/pep-0584/).
### [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") Examples and Recipes[¶](https://docs.python.org/3/library/collections.html#ordereddict-examples-and-recipes "Link to this heading")
It is straightforward to create an ordered dictionary variant that remembers the order the keys were *last* inserted. If a new entry overwrites an existing entry, the original insertion position is changed and moved to the end:
```
class LastUpdatedOrderedDict(OrderedDict):
'Store items in the order the keys were last added'
def __setitem__(self, key, value):
super().__setitem__(key, value)
self.move_to_end(key)
```
An [`OrderedDict`](https://docs.python.org/3/library/collections.html#collections.OrderedDict "collections.OrderedDict") would also be useful for implementing variants of [`functools.lru_cache()`](https://docs.python.org/3/library/functools.html#functools.lru_cache "functools.lru_cache"):
```
from collections import OrderedDict
from time import time
class TimeBoundedLRU:
"LRU Cache that invalidates and refreshes old entries."
def __init__(self, func, maxsize=128, maxage=30):
self.cache = OrderedDict() # { args : (timestamp, result)}
self.func = func
self.maxsize = maxsize
self.maxage = maxage
def __call__(self, *args):
if args in self.cache:
self.cache.move_to_end(args)
timestamp, result = self.cache[args]
if time() - timestamp <= self.maxage:
return result
result = self.func(*args)
self.cache[args] = time(), result
if len(self.cache) > self.maxsize:
self.cache.popitem(last=False)
return result
```
```
class MultiHitLRUCache:
""" LRU cache that defers caching a result until
it has been requested multiple times.
To avoid flushing the LRU cache with one-time requests,
we don't cache until a request has been made more than once.
"""
def __init__(self, func, maxsize=128, maxrequests=4096, cache_after=1):
self.requests = OrderedDict() # { uncached_key : request_count }
self.cache = OrderedDict() # { cached_key : function_result }
self.func = func
self.maxrequests = maxrequests # max number of uncached requests
self.maxsize = maxsize # max number of stored return values
self.cache_after = cache_after
def __call__(self, *args):
if args in self.cache:
self.cache.move_to_end(args)
return self.cache[args]
result = self.func(*args)
self.requests[args] = self.requests.get(args, 0) + 1
if self.requests[args] <= self.cache_after:
self.requests.move_to_end(args)
if len(self.requests) > self.maxrequests:
self.requests.popitem(last=False)
else:
self.requests.pop(args, None)
self.cache[args] = result
if len(self.cache) > self.maxsize:
self.cache.popitem(last=False)
return result
```
## [`UserDict`](https://docs.python.org/3/library/collections.html#collections.UserDict "collections.UserDict") objects[¶](https://docs.python.org/3/library/collections.html#userdict-objects "Link to this heading")
The class, [`UserDict`](https://docs.python.org/3/library/collections.html#collections.UserDict "collections.UserDict") acts as a wrapper around dictionary objects. The need for this class has been partially supplanted by the ability to subclass directly from [`dict`](https://docs.python.org/3/library/stdtypes.html#dict "dict"); however, this class can be easier to work with because the underlying dictionary is accessible as an attribute.
*class* collections.UserDict(*\*\*kwargs*)[¶](https://docs.python.org/3/library/collections.html#collections.UserDict "Link to this definition")
*class* collections.UserDict(*mapping*, */*, *\*\*kwargs*)
*class* collections.UserDict(*iterable*, */*, *\*\*kwargs*)
Class that simulates a dictionary. The instance’s contents are kept in a regular dictionary, which is accessible via the [`data`](https://docs.python.org/3/library/collections.html#collections.UserDict.data "collections.UserDict.data") attribute of `UserDict` instances. If arguments are provided, they are used to initialize `data`, like a regular dictionary.
In addition to supporting the methods and operations of mappings, `UserDict` instances provide the following attribute:
data[¶](https://docs.python.org/3/library/collections.html#collections.UserDict.data "Link to this definition")
A real dictionary used to store the contents of the `UserDict` class.
## [`UserList`](https://docs.python.org/3/library/collections.html#collections.UserList "collections.UserList") objects[¶](https://docs.python.org/3/library/collections.html#userlist-objects "Link to this heading")
This class acts as a wrapper around list objects. It is a useful base class for your own list-like classes which can inherit from them and override existing methods or add new ones. In this way, one can add new behaviors to lists.
The need for this class has been partially supplanted by the ability to subclass directly from [`list`](https://docs.python.org/3/library/stdtypes.html#list "list"); however, this class can be easier to work with because the underlying list is accessible as an attribute.
*class* collections.UserList(\[*list*\])[¶](https://docs.python.org/3/library/collections.html#collections.UserList "Link to this definition")
Class that simulates a list. The instance’s contents are kept in a regular list, which is accessible via the [`data`](https://docs.python.org/3/library/collections.html#collections.UserList.data "collections.UserList.data") attribute of `UserList` instances. The instance’s contents are initially set to a copy of *list*, defaulting to the empty list `[]`. *list* can be any iterable, for example a real Python list or a `UserList` object.
In addition to supporting the methods and operations of mutable sequences, `UserList` instances provide the following attribute:
data[¶](https://docs.python.org/3/library/collections.html#collections.UserList.data "Link to this definition")
A real [`list`](https://docs.python.org/3/library/stdtypes.html#list "list") object used to store the contents of the `UserList` class.
**Subclassing requirements:** Subclasses of [`UserList`](https://docs.python.org/3/library/collections.html#collections.UserList "collections.UserList") are expected to offer a constructor which can be called with either no arguments or one argument. List operations which return a new sequence attempt to create an instance of the actual implementation class. To do so, it assumes that the constructor can be called with a single parameter, which is a sequence object used as a data source.
If a derived class does not wish to comply with this requirement, all of the special methods supported by this class will need to be overridden; please consult the sources for information about the methods which need to be provided in that case.
## [`UserString`](https://docs.python.org/3/library/collections.html#collections.UserString "collections.UserString") objects[¶](https://docs.python.org/3/library/collections.html#userstring-objects "Link to this heading")
The class, [`UserString`](https://docs.python.org/3/library/collections.html#collections.UserString "collections.UserString") acts as a wrapper around string objects. The need for this class has been partially supplanted by the ability to subclass directly from [`str`](https://docs.python.org/3/library/stdtypes.html#str "str"); however, this class can be easier to work with because the underlying string is accessible as an attribute.
*class* collections.UserString(*seq*)[¶](https://docs.python.org/3/library/collections.html#collections.UserString "Link to this definition")
Class that simulates a string object. The instance’s content is kept in a regular string object, which is accessible via the [`data`](https://docs.python.org/3/library/collections.html#collections.UserString.data "collections.UserString.data") attribute of `UserString` instances. The instance’s contents are initially set to a copy of *seq*. The *seq* argument can be any object which can be converted into a string using the built-in [`str()`](https://docs.python.org/3/library/stdtypes.html#str "str") function.
In addition to supporting the methods and operations of strings, `UserString` instances provide the following attribute:
data[¶](https://docs.python.org/3/library/collections.html#collections.UserString.data "Link to this definition")
A real [`str`](https://docs.python.org/3/library/stdtypes.html#str "str") object used to store the contents of the `UserString` class.
Changed in version 3.5: New methods `__getnewargs__`, `__rmod__`, `casefold`, `format_map`, `isprintable`, and `maketrans`. | |||||||||
| ML Classification | ||||||||||
| ML Categories |
Raw JSON{
"/Computers_and_Electronics": 994,
"/Computers_and_Electronics/Programming": 828,
"/Computers_and_Electronics/Programming/Scripting_Languages": 791
} | |||||||||
| ML Page Types |
Raw JSON{
"/Document": 928,
"/Document/Manual": 910
} | |||||||||
| ML Intent Types |
Raw JSON{
"Informational": 997
} | |||||||||
| Content Metadata | ||||||||||
| Language | en | |||||||||
| Author | null | |||||||||
| Publish Time | not set | |||||||||
| Original Publish Time | 2014-04-05 01:30:14 (12 years ago) | |||||||||
| Republished | No | |||||||||
| Word Count (Total) | 8,596 | |||||||||
| Word Count (Content) | 8,072 | |||||||||
| Links | ||||||||||
| External Links | 12 | |||||||||
| Internal Links | 38 | |||||||||
| Technical SEO | ||||||||||
| Meta Nofollow | No | |||||||||
| Meta Noarchive | No | |||||||||
| JS Rendered | Yes | |||||||||
| Redirect Target | null | |||||||||
| Performance | ||||||||||
| Download Time (ms) | 21 | |||||||||
| TTFB (ms) | 19 | |||||||||
| Download Size (bytes) | 28,718 | |||||||||
| Shard | 16 (laksa) | |||||||||
| Root Hash | 10954876678907435016 | |||||||||
| Unparsed URL | org,python!docs,/3/library/collections.html s443 | |||||||||