mirror of
https://github.com/python/cpython.git
synced 2025-07-23 03:05:38 +00:00

svn+ssh://pythondev@svn.python.org/python/trunk ........ r70712 | benjamin.peterson | 2009-03-30 10:15:38 -0500 (Mon, 30 Mar 2009) | 1 line don't rely on the order dict repr #5605 ........ r70714 | brett.cannon | 2009-03-30 10:20:53 -0500 (Mon, 30 Mar 2009) | 1 line Add an entry to developers.txt. ........ r70764 | martin.v.loewis | 2009-03-30 17:06:33 -0500 (Mon, 30 Mar 2009) | 2 lines Add several VM developers. ........ r70765 | georg.brandl | 2009-03-30 17:09:34 -0500 (Mon, 30 Mar 2009) | 1 line #5199: make warning about vars() assignment more visible. ........ r70769 | andrew.kuchling | 2009-03-30 17:29:53 -0500 (Mon, 30 Mar 2009) | 1 line Remove comment ........ r70770 | andrew.kuchling | 2009-03-30 17:30:20 -0500 (Mon, 30 Mar 2009) | 1 line Add several items and placeholders ........ r70771 | andrew.kuchling | 2009-03-30 17:31:11 -0500 (Mon, 30 Mar 2009) | 1 line Many edits ........ r70773 | georg.brandl | 2009-03-30 17:43:00 -0500 (Mon, 30 Mar 2009) | 1 line #5039: make it clear that the impl. note refers to CPython. ........ r70776 | andrew.kuchling | 2009-03-30 18:08:24 -0500 (Mon, 30 Mar 2009) | 1 line typo fix ........ r70777 | andrew.kuchling | 2009-03-30 18:09:46 -0500 (Mon, 30 Mar 2009) | 1 line Add more items ........ r70788 | andrew.kuchling | 2009-03-30 20:21:01 -0500 (Mon, 30 Mar 2009) | 1 line Add various items ........ r70789 | georg.brandl | 2009-03-30 20:25:15 -0500 (Mon, 30 Mar 2009) | 1 line Fix a wrong struct field assignment (docstring as closure). ........ r70824 | georg.brandl | 2009-03-31 10:43:20 -0500 (Tue, 31 Mar 2009) | 1 line #5519: remove reference to Kodos, which seems dead. ........ r70828 | georg.brandl | 2009-03-31 10:50:16 -0500 (Tue, 31 Mar 2009) | 1 line #5581: fget argument of abstractproperty is optional as well. ........ r70832 | georg.brandl | 2009-03-31 11:31:11 -0500 (Tue, 31 Mar 2009) | 1 line #1386675: specify WindowsError as the exception, because it has a winerror attribute that EnvironmentError doesnt have. ........ r70836 | georg.brandl | 2009-03-31 11:50:25 -0500 (Tue, 31 Mar 2009) | 1 line #5417: replace references to undocumented functions by ones to documented functions. ........ r70842 | georg.brandl | 2009-03-31 12:13:06 -0500 (Tue, 31 Mar 2009) | 1 line #970783: document PyObject_Generic[GS]etAttr. ........ r70851 | georg.brandl | 2009-03-31 13:26:55 -0500 (Tue, 31 Mar 2009) | 1 line #837577: note cryptic return value of spawn*e on invalid env dicts. ........ r70855 | georg.brandl | 2009-03-31 13:30:37 -0500 (Tue, 31 Mar 2009) | 1 line #5245: note that PyRun_SimpleString doesnt return on SystemExit. ........ r70857 | georg.brandl | 2009-03-31 13:33:10 -0500 (Tue, 31 Mar 2009) | 1 line #5227: note that Py_Main doesnt return on SystemExit. ........ r70866 | georg.brandl | 2009-03-31 14:06:57 -0500 (Tue, 31 Mar 2009) | 1 line #4882: document named group behavior a bit better. ........ r70867 | georg.brandl | 2009-03-31 14:10:35 -0500 (Tue, 31 Mar 2009) | 1 line #1096310: document usage of sys.__std*__ a bit better. ........ r70868 | georg.brandl | 2009-03-31 14:12:17 -0500 (Tue, 31 Mar 2009) | 1 line #5190: export make_option in __all__. ........ r70869 | georg.brandl | 2009-03-31 14:14:42 -0500 (Tue, 31 Mar 2009) | 1 line Fix-up unwanted change. ........ r70870 | georg.brandl | 2009-03-31 14:26:24 -0500 (Tue, 31 Mar 2009) | 1 line #4411: document mro() and __mro__. (I hope I got it right.) ........ r70871 | georg.brandl | 2009-03-31 14:30:56 -0500 (Tue, 31 Mar 2009) | 1 line #5618: fix typo. ........ r70872 | r.david.murray | 2009-03-31 14:31:17 -0500 (Tue, 31 Mar 2009) | 3 lines Delete out-of-date and little-known README from the test directory by consensus of devs at pycon sprint. ........ r70883 | georg.brandl | 2009-03-31 15:41:08 -0500 (Tue, 31 Mar 2009) | 1 line #1674032: return value of flag from Event.wait(). OKed by Guido. ........ r70885 | tarek.ziade | 2009-03-31 15:48:31 -0500 (Tue, 31 Mar 2009) | 1 line using log.warn for sys.stderr ........ r70893 | georg.brandl | 2009-03-31 15:56:32 -0500 (Tue, 31 Mar 2009) | 1 line #1530012: move TQS section before raw strings. ........ r70894 | benjamin.peterson | 2009-03-31 16:06:30 -0500 (Tue, 31 Mar 2009) | 1 line take the usual lock precautions around _active_limbo_lock ........ r70896 | georg.brandl | 2009-03-31 16:15:33 -0500 (Tue, 31 Mar 2009) | 1 line #5598: document DocFileSuite *args argument. ........ r70897 | benjamin.peterson | 2009-03-31 16:34:42 -0500 (Tue, 31 Mar 2009) | 1 line fix Thread.ident when it is the main thread or a dummy thread #5632 ........ r70903 | georg.brandl | 2009-03-31 16:45:18 -0500 (Tue, 31 Mar 2009) | 1 line #1676135: remove trailing slashes from --prefix argument. ........ r70905 | georg.brandl | 2009-03-31 17:03:40 -0500 (Tue, 31 Mar 2009) | 1 line #5563: more documentation for bdist_msi. ........ r70906 | georg.brandl | 2009-03-31 17:11:53 -0500 (Tue, 31 Mar 2009) | 1 line #1651995: fix _convert_ref for non-ASCII characters. ........ r70907 | georg.brandl | 2009-03-31 17:18:19 -0500 (Tue, 31 Mar 2009) | 1 line #3427: document correct return type for urlopen().info(). ........ r70915 | georg.brandl | 2009-03-31 17:40:16 -0500 (Tue, 31 Mar 2009) | 1 line #5018: remove confusing paragraph. ........ r70927 | georg.brandl | 2009-03-31 18:01:27 -0500 (Tue, 31 Mar 2009) | 1 line Dont shout to users. ........ r70933 | georg.brandl | 2009-03-31 19:04:33 -0500 (Tue, 31 Mar 2009) | 2 lines Issue #5635: Fix running test_sys with tracing enabled. ........ r70951 | georg.brandl | 2009-04-01 09:02:27 -0500 (Wed, 01 Apr 2009) | 1 line Add Maksim, who worked on several issues at the sprint. ........ r70960 | jesse.noller | 2009-04-01 11:42:19 -0500 (Wed, 01 Apr 2009) | 1 line Issue 3270: document Listener address restrictions on windows ........ r70962 | brett.cannon | 2009-04-01 12:07:16 -0500 (Wed, 01 Apr 2009) | 2 lines Ron DuPlain was given commit privileges at PyCon 2009 to work on 3to2. ........ r70963 | georg.brandl | 2009-04-01 12:46:01 -0500 (Wed, 01 Apr 2009) | 1 line #5655: fix docstring oversight. ........ r70964 | brett.cannon | 2009-04-01 12:52:13 -0500 (Wed, 01 Apr 2009) | 2 lines Paul Kippes was given commit privileges to work on 3to2. ........ r70998 | georg.brandl | 2009-04-01 16:54:21 -0500 (Wed, 01 Apr 2009) | 1 line In Pdb, stop assigning values to __builtin__._ which interferes with the one commonly installed by gettext. ........ r71001 | brett.cannon | 2009-04-01 18:01:12 -0500 (Wed, 01 Apr 2009) | 3 lines Add my initials to Misc/developers.txt. Names are now sorted by number of characters in the person's name. ........ r71006 | georg.brandl | 2009-04-01 18:32:17 -0500 (Wed, 01 Apr 2009) | 1 line Cache the f_locals dict of the current frame, since every access to frame.f_locals overrides its contents with the real locals which undoes modifications made by the debugging user. ........ r71008 | andrew.kuchling | 2009-04-01 19:02:14 -0500 (Wed, 01 Apr 2009) | 1 line Typo fix ........ r71010 | benjamin.peterson | 2009-04-01 19:11:52 -0500 (Wed, 01 Apr 2009) | 1 line fix markup ........ r71011 | benjamin.peterson | 2009-04-01 19:12:47 -0500 (Wed, 01 Apr 2009) | 1 line this should be :noindex: ........ r71019 | georg.brandl | 2009-04-01 21:00:01 -0500 (Wed, 01 Apr 2009) | 1 line Fix test_doctest, missed two assignments to curframe. ........ r71037 | r.david.murray | 2009-04-01 23:34:04 -0500 (Wed, 01 Apr 2009) | 6 lines Clarify that datetime strftime does not produce leap seconds and datetime strptime does not accept it in the strftime behavior section of the datetime docs. Closes issue 2568. ........ r71056 | georg.brandl | 2009-04-02 12:43:07 -0500 (Thu, 02 Apr 2009) | 2 lines Actually the displayhook should print the repr. ........ r71094 | vinay.sajip | 2009-04-03 05:23:18 -0500 (Fri, 03 Apr 2009) | 1 line Added warning about logging use from asynchronous signal handlers. ........ r71101 | andrew.kuchling | 2009-04-03 16:43:00 -0500 (Fri, 03 Apr 2009) | 1 line Add some items ........ r71102 | andrew.kuchling | 2009-04-03 16:44:49 -0500 (Fri, 03 Apr 2009) | 1 line Fix 'the the'; grammar fix ........ r71103 | andrew.kuchling | 2009-04-03 16:45:29 -0500 (Fri, 03 Apr 2009) | 1 line Fix 'the the' duplication ........ r71106 | vinay.sajip | 2009-04-03 16:58:16 -0500 (Fri, 03 Apr 2009) | 1 line Clarified warning about logging use from asynchronous signal handlers. ........ r71119 | raymond.hettinger | 2009-04-04 00:37:47 -0500 (Sat, 04 Apr 2009) | 1 line Add helpful link. ........ r71123 | r.david.murray | 2009-04-04 01:39:56 -0500 (Sat, 04 Apr 2009) | 2 lines Fix error in description of 'oct' (issue 5678). ........ r71149 | georg.brandl | 2009-04-04 08:42:39 -0500 (Sat, 04 Apr 2009) | 1 line #5642: clarify map() compatibility to the builtin. ........ r71150 | georg.brandl | 2009-04-04 08:45:49 -0500 (Sat, 04 Apr 2009) | 1 line #5601: clarify that webbrowser is not meant for file names. ........ r71203 | benjamin.peterson | 2009-04-04 18:46:34 -0500 (Sat, 04 Apr 2009) | 1 line note how using iter* are unsafe while mutating and document iter(dict) ........ r71212 | georg.brandl | 2009-04-05 05:24:20 -0500 (Sun, 05 Apr 2009) | 1 line #1742837: expand HTTP server docs, and fix SocketServer ones to document methods as methods, not functions. ........ r71214 | georg.brandl | 2009-04-05 05:29:57 -0500 (Sun, 05 Apr 2009) | 1 line Normalize spelling of Mac OS X. ........ r71215 | georg.brandl | 2009-04-05 05:32:26 -0500 (Sun, 05 Apr 2009) | 1 line Avoid sure signs of a diseased mind. ........ r71216 | georg.brandl | 2009-04-05 05:41:02 -0500 (Sun, 05 Apr 2009) | 1 line #1718017: document the relation of os.path and the posixpath, ntpath etc. modules better. ........ r71217 | georg.brandl | 2009-04-05 05:48:47 -0500 (Sun, 05 Apr 2009) | 1 line #1726172: dont raise an unexpected IndexError if a voidresp() call has an empty response. ........ r71221 | vinay.sajip | 2009-04-05 06:06:24 -0500 (Sun, 05 Apr 2009) | 1 line Issue #5695: Moved logging.captureWarnings() call inside with statement in WarningsTest.test_warnings. ........ r71240 | georg.brandl | 2009-04-05 09:40:06 -0500 (Sun, 05 Apr 2009) | 1 line #5370: doc update about unpickling objects with custom __getattr__ etc. methods. ........
624 lines
20 KiB
ReStructuredText
624 lines
20 KiB
ReStructuredText
.. _tut-structures:
|
|
|
|
***************
|
|
Data Structures
|
|
***************
|
|
|
|
This chapter describes some things you've learned about already in more detail,
|
|
and adds some new things as well.
|
|
|
|
.. _tut-morelists:
|
|
|
|
More on Lists
|
|
=============
|
|
|
|
The list data type has some more methods. Here are all of the methods of list
|
|
objects:
|
|
|
|
|
|
.. method:: list.append(x)
|
|
:noindex:
|
|
|
|
Add an item to the end of the list; equivalent to ``a[len(a):] = [x]``.
|
|
|
|
|
|
.. method:: list.extend(L)
|
|
:noindex:
|
|
|
|
Extend the list by appending all the items in the given list; equivalent to
|
|
``a[len(a):] = L``.
|
|
|
|
|
|
.. method:: list.insert(i, x)
|
|
:noindex:
|
|
|
|
Insert an item at a given position. The first argument is the index of the
|
|
element before which to insert, so ``a.insert(0, x)`` inserts at the front of
|
|
the list, and ``a.insert(len(a), x)`` is equivalent to ``a.append(x)``.
|
|
|
|
|
|
.. method:: list.remove(x)
|
|
:noindex:
|
|
|
|
Remove the first item from the list whose value is *x*. It is an error if there
|
|
is no such item.
|
|
|
|
|
|
.. method:: list.pop([i])
|
|
:noindex:
|
|
|
|
Remove the item at the given position in the list, and return it. If no index
|
|
is specified, ``a.pop()`` removes and returns the last item in the list. (The
|
|
square brackets around the *i* in the method signature denote that the parameter
|
|
is optional, not that you should type square brackets at that position. You
|
|
will see this notation frequently in the Python Library Reference.)
|
|
|
|
|
|
.. method:: list.index(x)
|
|
:noindex:
|
|
|
|
Return the index in the list of the first item whose value is *x*. It is an
|
|
error if there is no such item.
|
|
|
|
|
|
.. method:: list.count(x)
|
|
:noindex:
|
|
|
|
Return the number of times *x* appears in the list.
|
|
|
|
|
|
.. method:: list.sort()
|
|
:noindex:
|
|
|
|
Sort the items of the list, in place.
|
|
|
|
|
|
.. method:: list.reverse()
|
|
:noindex:
|
|
|
|
Reverse the elements of the list, in place.
|
|
|
|
An example that uses most of the list methods::
|
|
|
|
>>> a = [66.25, 333, 333, 1, 1234.5]
|
|
>>> print(a.count(333), a.count(66.25), a.count('x'))
|
|
2 1 0
|
|
>>> a.insert(2, -1)
|
|
>>> a.append(333)
|
|
>>> a
|
|
[66.25, 333, -1, 333, 1, 1234.5, 333]
|
|
>>> a.index(333)
|
|
1
|
|
>>> a.remove(333)
|
|
>>> a
|
|
[66.25, -1, 333, 1, 1234.5, 333]
|
|
>>> a.reverse()
|
|
>>> a
|
|
[333, 1234.5, 1, 333, -1, 66.25]
|
|
>>> a.sort()
|
|
>>> a
|
|
[-1, 1, 66.25, 333, 333, 1234.5]
|
|
|
|
|
|
.. _tut-lists-as-stacks:
|
|
|
|
Using Lists as Stacks
|
|
---------------------
|
|
|
|
.. sectionauthor:: Ka-Ping Yee <ping@lfw.org>
|
|
|
|
|
|
The list methods make it very easy to use a list as a stack, where the last
|
|
element added is the first element retrieved ("last-in, first-out"). To add an
|
|
item to the top of the stack, use :meth:`append`. To retrieve an item from the
|
|
top of the stack, use :meth:`pop` without an explicit index. For example::
|
|
|
|
>>> stack = [3, 4, 5]
|
|
>>> stack.append(6)
|
|
>>> stack.append(7)
|
|
>>> stack
|
|
[3, 4, 5, 6, 7]
|
|
>>> stack.pop()
|
|
7
|
|
>>> stack
|
|
[3, 4, 5, 6]
|
|
>>> stack.pop()
|
|
6
|
|
>>> stack.pop()
|
|
5
|
|
>>> stack
|
|
[3, 4]
|
|
|
|
|
|
.. _tut-lists-as-queues:
|
|
|
|
Using Lists as Queues
|
|
---------------------
|
|
|
|
.. sectionauthor:: Ka-Ping Yee <ping@lfw.org>
|
|
|
|
|
|
You can also use a list conveniently as a queue, where the first element added
|
|
is the first element retrieved ("first-in, first-out"). To add an item to the
|
|
back of the queue, use :meth:`append`. To retrieve an item from the front of
|
|
the queue, use :meth:`pop` with ``0`` as the index. For example::
|
|
|
|
>>> queue = ["Eric", "John", "Michael"]
|
|
>>> queue.append("Terry") # Terry arrives
|
|
>>> queue.append("Graham") # Graham arrives
|
|
>>> queue.pop(0)
|
|
'Eric'
|
|
>>> queue.pop(0)
|
|
'John'
|
|
>>> queue
|
|
['Michael', 'Terry', 'Graham']
|
|
|
|
|
|
List Comprehensions
|
|
-------------------
|
|
|
|
List comprehensions provide a concise way to create lists from sequences.
|
|
Common applications are to make lists where each element is the result of
|
|
some operations applied to each member of the sequence, or to create a
|
|
subsequence of those elements that satisfy a certain condition.
|
|
|
|
|
|
Each list comprehension consists of an expression followed by a :keyword:`for`
|
|
clause, then zero or more :keyword:`for` or :keyword:`if` clauses. The result
|
|
will be a list resulting from evaluating the expression in the context of the
|
|
:keyword:`for` and :keyword:`if` clauses which follow it. If the expression
|
|
would evaluate to a tuple, it must be parenthesized.
|
|
|
|
Here we take a list of numbers and return a list of three times each number::
|
|
|
|
>>> vec = [2, 4, 6]
|
|
>>> [3*x for x in vec]
|
|
[6, 12, 18]
|
|
|
|
Now we get a little fancier::
|
|
|
|
>>> [[x, x**2] for x in vec]
|
|
[[2, 4], [4, 16], [6, 36]]
|
|
|
|
Here we apply a method call to each item in a sequence::
|
|
|
|
>>> freshfruit = [' banana', ' loganberry ', 'passion fruit ']
|
|
>>> [weapon.strip() for weapon in freshfruit]
|
|
['banana', 'loganberry', 'passion fruit']
|
|
|
|
Using the :keyword:`if` clause we can filter the stream::
|
|
|
|
>>> [3*x for x in vec if x > 3]
|
|
[12, 18]
|
|
>>> [3*x for x in vec if x < 2]
|
|
[]
|
|
|
|
Tuples can often be created without their parentheses, but not here::
|
|
|
|
>>> [x, x**2 for x in vec] # error - parens required for tuples
|
|
File "<stdin>", line 1, in ?
|
|
[x, x**2 for x in vec]
|
|
^
|
|
SyntaxError: invalid syntax
|
|
>>> [(x, x**2) for x in vec]
|
|
[(2, 4), (4, 16), (6, 36)]
|
|
|
|
Here are some nested for loops and other fancy behavior::
|
|
|
|
>>> vec1 = [2, 4, 6]
|
|
>>> vec2 = [4, 3, -9]
|
|
>>> [x*y for x in vec1 for y in vec2]
|
|
[8, 6, -18, 16, 12, -36, 24, 18, -54]
|
|
>>> [x+y for x in vec1 for y in vec2]
|
|
[6, 5, -7, 8, 7, -5, 10, 9, -3]
|
|
>>> [vec1[i]*vec2[i] for i in range(len(vec1))]
|
|
[8, 12, -54]
|
|
|
|
List comprehensions can be applied to complex expressions and nested functions::
|
|
|
|
>>> [str(round(355/113, i)) for i in range(1, 6)]
|
|
['3.1', '3.14', '3.142', '3.1416', '3.14159']
|
|
|
|
|
|
Nested List Comprehensions
|
|
--------------------------
|
|
|
|
If you've got the stomach for it, list comprehensions can be nested. They are a
|
|
powerful tool but -- like all powerful tools -- they need to be used carefully,
|
|
if at all.
|
|
|
|
Consider the following example of a 3x3 matrix held as a list containing three
|
|
lists, one list per row::
|
|
|
|
>>> mat = [
|
|
... [1, 2, 3],
|
|
... [4, 5, 6],
|
|
... [7, 8, 9],
|
|
... ]
|
|
|
|
Now, if you wanted to swap rows and columns, you could use a list
|
|
comprehension::
|
|
|
|
>>> print([[row[i] for row in mat] for i in [0, 1, 2]])
|
|
[[1, 4, 7], [2, 5, 8], [3, 6, 9]]
|
|
|
|
Special care has to be taken for the *nested* list comprehension:
|
|
|
|
To avoid apprehension when nesting list comprehensions, read from right to
|
|
left.
|
|
|
|
A more verbose version of this snippet shows the flow explicitly::
|
|
|
|
for i in [0, 1, 2]:
|
|
for row in mat:
|
|
print(row[i], end="")
|
|
print()
|
|
|
|
In real world, you should prefer built-in functions to complex flow statements.
|
|
The :func:`zip` function would do a great job for this use case::
|
|
|
|
>>> list(zip(*mat))
|
|
[(1, 4, 7), (2, 5, 8), (3, 6, 9)]
|
|
|
|
See :ref:`tut-unpacking-arguments` for details on the asterisk in this line.
|
|
|
|
.. _tut-del:
|
|
|
|
The :keyword:`del` statement
|
|
============================
|
|
|
|
There is a way to remove an item from a list given its index instead of its
|
|
value: the :keyword:`del` statement. This differs from the :meth:`pop` method
|
|
which returns a value. The :keyword:`del` statement can also be used to remove
|
|
slices from a list or clear the entire list (which we did earlier by assignment
|
|
of an empty list to the slice). For example::
|
|
|
|
>>> a = [-1, 1, 66.25, 333, 333, 1234.5]
|
|
>>> del a[0]
|
|
>>> a
|
|
[1, 66.25, 333, 333, 1234.5]
|
|
>>> del a[2:4]
|
|
>>> a
|
|
[1, 66.25, 1234.5]
|
|
>>> del a[:]
|
|
>>> a
|
|
[]
|
|
|
|
:keyword:`del` can also be used to delete entire variables::
|
|
|
|
>>> del a
|
|
|
|
Referencing the name ``a`` hereafter is an error (at least until another value
|
|
is assigned to it). We'll find other uses for :keyword:`del` later.
|
|
|
|
|
|
.. _tut-tuples:
|
|
|
|
Tuples and Sequences
|
|
====================
|
|
|
|
We saw that lists and strings have many common properties, such as indexing and
|
|
slicing operations. They are two examples of *sequence* data types (see
|
|
:ref:`typesseq`). Since Python is an evolving language, other sequence data
|
|
types may be added. There is also another standard sequence data type: the
|
|
*tuple*.
|
|
|
|
A tuple consists of a number of values separated by commas, for instance::
|
|
|
|
>>> t = 12345, 54321, 'hello!'
|
|
>>> t[0]
|
|
12345
|
|
>>> t
|
|
(12345, 54321, 'hello!')
|
|
>>> # Tuples may be nested:
|
|
... u = t, (1, 2, 3, 4, 5)
|
|
>>> u
|
|
((12345, 54321, 'hello!'), (1, 2, 3, 4, 5))
|
|
|
|
As you see, on output tuples are always enclosed in parentheses, so that nested
|
|
tuples are interpreted correctly; they may be input with or without surrounding
|
|
parentheses, although often parentheses are necessary anyway (if the tuple is
|
|
part of a larger expression).
|
|
|
|
Tuples have many uses. For example: (x, y) coordinate pairs, employee records
|
|
from a database, etc. Tuples, like strings, are immutable: it is not possible
|
|
to assign to the individual items of a tuple (you can simulate much of the same
|
|
effect with slicing and concatenation, though). It is also possible to create
|
|
tuples which contain mutable objects, such as lists.
|
|
|
|
A special problem is the construction of tuples containing 0 or 1 items: the
|
|
syntax has some extra quirks to accommodate these. Empty tuples are constructed
|
|
by an empty pair of parentheses; a tuple with one item is constructed by
|
|
following a value with a comma (it is not sufficient to enclose a single value
|
|
in parentheses). Ugly, but effective. For example::
|
|
|
|
>>> empty = ()
|
|
>>> singleton = 'hello', # <-- note trailing comma
|
|
>>> len(empty)
|
|
0
|
|
>>> len(singleton)
|
|
1
|
|
>>> singleton
|
|
('hello',)
|
|
|
|
The statement ``t = 12345, 54321, 'hello!'`` is an example of *tuple packing*:
|
|
the values ``12345``, ``54321`` and ``'hello!'`` are packed together in a tuple.
|
|
The reverse operation is also possible::
|
|
|
|
>>> x, y, z = t
|
|
|
|
This is called, appropriately enough, *sequence unpacking* and works for any
|
|
sequence on the right-hand side. Sequence unpacking requires the list of
|
|
variables on the left to have the same number of elements as the length of the
|
|
sequence. Note that multiple assignment is really just a combination of tuple
|
|
packing and sequence unpacking.
|
|
|
|
.. XXX Add a bit on the difference between tuples and lists.
|
|
|
|
|
|
.. _tut-sets:
|
|
|
|
Sets
|
|
====
|
|
|
|
Python also includes a data type for *sets*. A set is an unordered collection
|
|
with no duplicate elements. Basic uses include membership testing and
|
|
eliminating duplicate entries. Set objects also support mathematical operations
|
|
like union, intersection, difference, and symmetric difference.
|
|
|
|
Curly braces or the :func:`set` function can be use to create sets. Note:
|
|
To create an empty set you have to use set(), not {}; the latter creates
|
|
an empty dictionary, a data structure that we discuss in the next section.
|
|
|
|
Here is a brief demonstration::
|
|
|
|
>>> basket = {'apple', 'orange', 'apple', 'pear', 'orange', 'banana'}
|
|
>>> print(basket)
|
|
{'orange', 'banana', 'pear', 'apple'}
|
|
>>> fruit = ['apple', 'orange', 'apple', 'pear', 'orange', 'banana']
|
|
>>> fruit = set(basket) # create a set without duplicates
|
|
>>> fruit
|
|
{'orange', 'pear', 'apple', 'banana'}
|
|
>>> fruit = {'orange', 'apple'} # {} syntax is equivalent to [] for lists
|
|
>>> fruit
|
|
{'orange', 'apple'}
|
|
>>> 'orange' in fruit # fast membership testing
|
|
True
|
|
>>> 'crabgrass' in fruit
|
|
False
|
|
|
|
>>> # Demonstrate set operations on unique letters from two words
|
|
...
|
|
>>> a = set('abracadabra')
|
|
>>> b = set('alacazam')
|
|
>>> a # unique letters in a
|
|
{'a', 'r', 'b', 'c', 'd'}
|
|
>>> a - b # letters in a but not in b
|
|
{'r', 'd', 'b'}
|
|
>>> a | b # letters in either a or b
|
|
{'a', 'c', 'r', 'd', 'b', 'm', 'z', 'l'}
|
|
>>> a & b # letters in both a and b
|
|
{'a', 'c'}
|
|
>>> a ^ b # letters in a or b but not both
|
|
{'r', 'd', 'b', 'm', 'z', 'l'}
|
|
|
|
Like for lists, there is a set comprehension syntax::
|
|
|
|
>>> a = {x for x in 'abracadabra' if x not in 'abc'}
|
|
>>> a
|
|
{'r', 'd'}
|
|
|
|
|
|
|
|
.. _tut-dictionaries:
|
|
|
|
Dictionaries
|
|
============
|
|
|
|
Another useful data type built into Python is the *dictionary* (see
|
|
:ref:`typesmapping`). Dictionaries are sometimes found in other languages as
|
|
"associative memories" or "associative arrays". Unlike sequences, which are
|
|
indexed by a range of numbers, dictionaries are indexed by *keys*, which can be
|
|
any immutable type; strings and numbers can always be keys. Tuples can be used
|
|
as keys if they contain only strings, numbers, or tuples; if a tuple contains
|
|
any mutable object either directly or indirectly, it cannot be used as a key.
|
|
You can't use lists as keys, since lists can be modified in place using index
|
|
assignments, slice assignments, or methods like :meth:`append` and
|
|
:meth:`extend`.
|
|
|
|
It is best to think of a dictionary as an unordered set of *key: value* pairs,
|
|
with the requirement that the keys are unique (within one dictionary). A pair of
|
|
braces creates an empty dictionary: ``{}``. Placing a comma-separated list of
|
|
key:value pairs within the braces adds initial key:value pairs to the
|
|
dictionary; this is also the way dictionaries are written on output.
|
|
|
|
The main operations on a dictionary are storing a value with some key and
|
|
extracting the value given the key. It is also possible to delete a key:value
|
|
pair with ``del``. If you store using a key that is already in use, the old
|
|
value associated with that key is forgotten. It is an error to extract a value
|
|
using a non-existent key.
|
|
|
|
Performing ``list(d.keys())`` on a dictionary returns a list of all the keys
|
|
used in the dictionary, in arbitrary order (if you want it sorted, just apply
|
|
the :meth:`sorted` function instead). To check whether a single key is
|
|
in the dictionary, use the :keyword:`in` keyword.
|
|
|
|
Here is a small example using a dictionary::
|
|
|
|
>>> tel = {'jack': 4098, 'sape': 4139}
|
|
>>> tel['guido'] = 4127
|
|
>>> tel
|
|
{'sape': 4139, 'guido': 4127, 'jack': 4098}
|
|
>>> tel['jack']
|
|
4098
|
|
>>> del tel['sape']
|
|
>>> tel['irv'] = 4127
|
|
>>> tel
|
|
{'guido': 4127, 'irv': 4127, 'jack': 4098}
|
|
>>> list(tel.keys())
|
|
['irv', 'guido', 'jack']
|
|
>>> sorted(tel.keys())
|
|
['guido', 'irv', 'jack']
|
|
>>> 'guido' in tel
|
|
True
|
|
>>> 'jack' not in tel
|
|
False
|
|
|
|
The :func:`dict` constructor builds dictionaries directly from lists of
|
|
key-value pairs stored as tuples. When the pairs form a pattern, list
|
|
comprehensions can compactly specify the key-value list. ::
|
|
|
|
>>> dict([('sape', 4139), ('guido', 4127), ('jack', 4098)])
|
|
{'sape': 4139, 'jack': 4098, 'guido': 4127}
|
|
|
|
In addition, dict comprehensions can be used to create dictionaries from
|
|
arbitrary key and value expressions::
|
|
|
|
>>> {x: x**2 for x in (2, 4, 6)}
|
|
{2: 4, 4: 16, 6: 36}
|
|
|
|
When the keys are simple strings, it is sometimes easier to specify pairs using
|
|
keyword arguments::
|
|
|
|
>>> dict(sape=4139, guido=4127, jack=4098)
|
|
{'sape': 4139, 'jack': 4098, 'guido': 4127}
|
|
|
|
|
|
.. XXX Find out the right way to do these DUBOIS
|
|
.. _tut-loopidioms:
|
|
|
|
Looping Techniques
|
|
==================
|
|
|
|
When looping through dictionaries, the key and corresponding value can be
|
|
retrieved at the same time using the :meth:`items` method. ::
|
|
|
|
>>> knights = {'gallahad': 'the pure', 'robin': 'the brave'}
|
|
>>> for k, v in knights.items():
|
|
... print(k, v)
|
|
...
|
|
gallahad the pure
|
|
robin the brave
|
|
|
|
When looping through a sequence, the position index and corresponding value can
|
|
be retrieved at the same time using the :func:`enumerate` function. ::
|
|
|
|
>>> for i, v in enumerate(['tic', 'tac', 'toe']):
|
|
... print(i, v)
|
|
...
|
|
0 tic
|
|
1 tac
|
|
2 toe
|
|
|
|
To loop over two or more sequences at the same time, the entries can be paired
|
|
with the :func:`zip` function. ::
|
|
|
|
>>> questions = ['name', 'quest', 'favorite color']
|
|
>>> answers = ['lancelot', 'the holy grail', 'blue']
|
|
>>> for q, a in zip(questions, answers):
|
|
... print('What is your {0}? It is {1}.'.format(q, a))
|
|
...
|
|
What is your name? It is lancelot.
|
|
What is your quest? It is the holy grail.
|
|
What is your favorite color? It is blue.
|
|
|
|
To loop over a sequence in reverse, first specify the sequence in a forward
|
|
direction and then call the :func:`reversed` function. ::
|
|
|
|
>>> for i in reversed(range(1, 10, 2)):
|
|
... print(i)
|
|
...
|
|
9
|
|
7
|
|
5
|
|
3
|
|
1
|
|
|
|
To loop over a sequence in sorted order, use the :func:`sorted` function which
|
|
returns a new sorted list while leaving the source unaltered. ::
|
|
|
|
>>> basket = ['apple', 'orange', 'apple', 'pear', 'orange', 'banana']
|
|
>>> for f in sorted(set(basket)):
|
|
... print(f)
|
|
...
|
|
apple
|
|
banana
|
|
orange
|
|
pear
|
|
|
|
|
|
.. _tut-conditions:
|
|
|
|
More on Conditions
|
|
==================
|
|
|
|
The conditions used in ``while`` and ``if`` statements can contain any
|
|
operators, not just comparisons.
|
|
|
|
The comparison operators ``in`` and ``not in`` check whether a value occurs
|
|
(does not occur) in a sequence. The operators ``is`` and ``is not`` compare
|
|
whether two objects are really the same object; this only matters for mutable
|
|
objects like lists. All comparison operators have the same priority, which is
|
|
lower than that of all numerical operators.
|
|
|
|
Comparisons can be chained. For example, ``a < b == c`` tests whether ``a`` is
|
|
less than ``b`` and moreover ``b`` equals ``c``.
|
|
|
|
Comparisons may be combined using the Boolean operators ``and`` and ``or``, and
|
|
the outcome of a comparison (or of any other Boolean expression) may be negated
|
|
with ``not``. These have lower priorities than comparison operators; between
|
|
them, ``not`` has the highest priority and ``or`` the lowest, so that ``A and
|
|
not B or C`` is equivalent to ``(A and (not B)) or C``. As always, parentheses
|
|
can be used to express the desired composition.
|
|
|
|
The Boolean operators ``and`` and ``or`` are so-called *short-circuit*
|
|
operators: their arguments are evaluated from left to right, and evaluation
|
|
stops as soon as the outcome is determined. For example, if ``A`` and ``C`` are
|
|
true but ``B`` is false, ``A and B and C`` does not evaluate the expression
|
|
``C``. When used as a general value and not as a Boolean, the return value of a
|
|
short-circuit operator is the last evaluated argument.
|
|
|
|
It is possible to assign the result of a comparison or other Boolean expression
|
|
to a variable. For example, ::
|
|
|
|
>>> string1, string2, string3 = '', 'Trondheim', 'Hammer Dance'
|
|
>>> non_null = string1 or string2 or string3
|
|
>>> non_null
|
|
'Trondheim'
|
|
|
|
Note that in Python, unlike C, assignment cannot occur inside expressions. C
|
|
programmers may grumble about this, but it avoids a common class of problems
|
|
encountered in C programs: typing ``=`` in an expression when ``==`` was
|
|
intended.
|
|
|
|
|
|
.. _tut-comparing:
|
|
|
|
Comparing Sequences and Other Types
|
|
===================================
|
|
|
|
Sequence objects may be compared to other objects with the same sequence type.
|
|
The comparison uses *lexicographical* ordering: first the first two items are
|
|
compared, and if they differ this determines the outcome of the comparison; if
|
|
they are equal, the next two items are compared, and so on, until either
|
|
sequence is exhausted. If two items to be compared are themselves sequences of
|
|
the same type, the lexicographical comparison is carried out recursively. If
|
|
all items of two sequences compare equal, the sequences are considered equal.
|
|
If one sequence is an initial sub-sequence of the other, the shorter sequence is
|
|
the smaller (lesser) one. Lexicographical ordering for strings uses the ASCII
|
|
ordering for individual characters. Some examples of comparisons between
|
|
sequences of the same type::
|
|
|
|
(1, 2, 3) < (1, 2, 4)
|
|
[1, 2, 3] < [1, 2, 4]
|
|
'ABC' < 'C' < 'Pascal' < 'Python'
|
|
(1, 2, 3, 4) < (1, 2, 4)
|
|
(1, 2) < (1, 2, -1)
|
|
(1, 2, 3) == (1.0, 2.0, 3.0)
|
|
(1, 2, ('aa', 'ab')) < (1, 2, ('abc', 'a'), 4)
|
|
|
|
Note that comparing objects of different types with ``<`` or ``>`` is legal
|
|
provided that the objects have appropriate comparison methods. For example,
|
|
mixed numeric types are compared according to their numeric value, so 0 equals
|
|
0.0, etc. Otherwise, rather than providing an arbitrary ordering, the
|
|
interpreter will raise a :exc:`TypeError` exception.
|