Admin Control Panel v2.0

✎ Editing: programming.html ← Back

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 
 <title>Programming FAQ &mdash; Python 2.7.5 documentation</title>
 
 <link rel="stylesheet" href="../_static/default.css" type="text/css" />
 <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
 
 <script type="text/javascript">
 var DOCUMENTATION_OPTIONS = {
 URL_ROOT: '../',
 VERSION: '2.7.5',
 COLLAPSE_INDEX: false,
 FILE_SUFFIX: '.html',
 HAS_SOURCE: true
 };
 </script>
 <script type="text/javascript" src="../_static/jquery.js"></script>
 <script type="text/javascript" src="../_static/underscore.js"></script>
 <script type="text/javascript" src="../_static/doctools.js"></script>
 <script type="text/javascript" src="../_static/sidebar.js"></script>
 <link rel="search" type="application/opensearchdescription+xml"
 title="Search within Python 2.7.5 documentation"
 href="../_static/opensearch.xml"/>
 <link rel="author" title="About these documents" href="../about.html" />
 <link rel="copyright" title="Copyright" href="../copyright.html" />
 <link rel="top" title="Python 2.7.5 documentation" href="../index.html" />
 <link rel="up" title="Python Frequently Asked Questions" href="index.html" />
 <link rel="next" title="Design and History FAQ" href="design.html" />
 <link rel="prev" title="General Python FAQ" href="general.html" />
 <link rel="shortcut icon" type="image/png" href="../_static/py.png" />
 <script type="text/javascript" src="../_static/copybutton.js"></script>

</head>
 <body>
 <div class="related">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 accesskey="I">index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="design.html" title="Design and History FAQ"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="general.html" title="General Python FAQ"
 accesskey="P">previous</a> |</li>
 <li><img src="../_static/py.png" alt=""
 style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="http://www.python.org/">Python</a> &raquo;</li>
 <li>
 <a href="../index.html">Python 2.7.5 documentation</a> &raquo;
 </li>

<li><a href="index.html" accesskey="U">Python Frequently Asked Questions</a> &raquo;</li> 
 </ul>
 </div>

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body">
 
 <div class="section" id="programming-faq">
<h1><a class="toc-backref" href="#id1">Programming FAQ</a><a class="headerlink" href="#programming-faq" title="Permalink to this headline">¶</a></h1>
<div class="contents topic" id="contents">
Contents
<ul class="simple">
<li><a class="reference internal" href="#programming-faq" id="id1">Programming FAQ</a><ul>
<li><a class="reference internal" href="#general-questions" id="id2">General Questions</a><ul>
<li><a class="reference internal" href="#is-there-a-source-code-level-debugger-with-breakpoints-single-stepping-etc" id="id3">Is there a source code level debugger with breakpoints, single-stepping, etc.?</a></li>
<li><a class="reference internal" href="#is-there-a-tool-to-help-find-bugs-or-perform-static-analysis" id="id4">Is there a tool to help find bugs or perform static analysis?</a></li>
<li><a class="reference internal" href="#how-can-i-create-a-stand-alone-binary-from-a-python-script" id="id5">How can I create a stand-alone binary from a Python script?</a></li>
<li><a class="reference internal" href="#are-there-coding-standards-or-a-style-guide-for-python-programs" id="id6">Are there coding standards or a style guide for Python programs?</a></li>
<li><a class="reference internal" href="#my-program-is-too-slow-how-do-i-speed-it-up" id="id7">My program is too slow. How do I speed it up?</a></li>
</ul>
</li>
<li><a class="reference internal" href="#core-language" id="id8">Core Language</a><ul>
<li><a class="reference internal" href="#why-am-i-getting-an-unboundlocalerror-when-the-variable-has-a-value" id="id9">Why am I getting an UnboundLocalError when the variable has a value?</a></li>
<li><a class="reference internal" href="#what-are-the-rules-for-local-and-global-variables-in-python" id="id10">What are the rules for local and global variables in Python?</a></li>
<li><a class="reference internal" href="#why-do-lambdas-defined-in-a-loop-with-different-values-all-return-the-same-result" id="id11">Why do lambdas defined in a loop with different values all return the same result?</a></li>
<li><a class="reference internal" href="#how-do-i-share-global-variables-across-modules" id="id12">How do I share global variables across modules?</a></li>
<li><a class="reference internal" href="#what-are-the-best-practices-for-using-import-in-a-module" id="id13">What are the &#8220;best practices&#8221; for using import in a module?</a></li>
<li><a class="reference internal" href="#how-can-i-pass-optional-or-keyword-parameters-from-one-function-to-another" id="id14">How can I pass optional or keyword parameters from one function to another?</a></li>
<li><a class="reference internal" href="#what-is-the-difference-between-arguments-and-parameters" id="id15">What is the difference between arguments and parameters?</a></li>
<li><a class="reference internal" href="#how-do-i-write-a-function-with-output-parameters-call-by-reference" id="id16">How do I write a function with output parameters (call by reference)?</a></li>
<li><a class="reference internal" href="#how-do-you-make-a-higher-order-function-in-python" id="id17">How do you make a higher order function in Python?</a></li>
<li><a class="reference internal" href="#how-do-i-copy-an-object-in-python" id="id18">How do I copy an object in Python?</a></li>
<li><a class="reference internal" href="#how-can-i-find-the-methods-or-attributes-of-an-object" id="id19">How can I find the methods or attributes of an object?</a></li>
<li><a class="reference internal" href="#how-can-my-code-discover-the-name-of-an-object" id="id20">How can my code discover the name of an object?</a></li>
<li><a class="reference internal" href="#what-s-up-with-the-comma-operator-s-precedence" id="id21">What&#8217;s up with the comma operator&#8217;s precedence?</a></li>
<li><a class="reference internal" href="#is-there-an-equivalent-of-c-s-ternary-operator" id="id22">Is there an equivalent of C&#8217;s &#8221;?:&#8221; ternary operator?</a></li>
<li><a class="reference internal" href="#is-it-possible-to-write-obfuscated-one-liners-in-python" id="id23">Is it possible to write obfuscated one-liners in Python?</a></li>
</ul>
</li>
<li><a class="reference internal" href="#numbers-and-strings" id="id24">Numbers and strings</a><ul>
<li><a class="reference internal" href="#how-do-i-specify-hexadecimal-and-octal-integers" id="id25">How do I specify hexadecimal and octal integers?</a></li>
<li><a class="reference internal" href="#why-does-22-10-return-3" id="id26">Why does -22 // 10 return -3?</a></li>
<li><a class="reference internal" href="#how-do-i-convert-a-string-to-a-number" id="id27">How do I convert a string to a number?</a></li>
<li><a class="reference internal" href="#how-do-i-convert-a-number-to-a-string" id="id28">How do I convert a number to a string?</a></li>
<li><a class="reference internal" href="#how-do-i-modify-a-string-in-place" id="id29">How do I modify a string in place?</a></li>
<li><a class="reference internal" href="#how-do-i-use-strings-to-call-functions-methods" id="id30">How do I use strings to call functions/methods?</a></li>
<li><a class="reference internal" href="#is-there-an-equivalent-to-perl-s-chomp-for-removing-trailing-newlines-from-strings" id="id31">Is there an equivalent to Perl&#8217;s chomp() for removing trailing newlines from strings?</a></li>
<li><a class="reference internal" href="#is-there-a-scanf-or-sscanf-equivalent" id="id32">Is there a scanf() or sscanf() equivalent?</a></li>
<li><a class="reference internal" href="#what-does-unicodeerror-ascii-decoding-encoding-error-ordinal-not-in-range-128-mean" id="id33">What does &#8216;UnicodeError: ASCII [decoding,encoding] error: ordinal not in range(128)&#8217; mean?</a></li>
</ul>
</li>
<li><a class="reference internal" href="#sequences-tuples-lists" id="id34">Sequences (Tuples/Lists)</a><ul>
<li><a class="reference internal" href="#how-do-i-convert-between-tuples-and-lists" id="id35">How do I convert between tuples and lists?</a></li>
<li><a class="reference internal" href="#what-s-a-negative-index" id="id36">What&#8217;s a negative index?</a></li>
<li><a class="reference internal" href="#how-do-i-iterate-over-a-sequence-in-reverse-order" id="id37">How do I iterate over a sequence in reverse order?</a></li>
<li><a class="reference internal" href="#how-do-you-remove-duplicates-from-a-list" id="id38">How do you remove duplicates from a list?</a></li>
<li><a class="reference internal" href="#how-do-you-make-an-array-in-python" id="id39">How do you make an array in Python?</a></li>
<li><a class="reference internal" href="#how-do-i-create-a-multidimensional-list" id="id40">How do I create a multidimensional list?</a></li>
<li><a class="reference internal" href="#how-do-i-apply-a-method-to-a-sequence-of-objects" id="id41">How do I apply a method to a sequence of objects?</a></li>
</ul>
</li>
<li><a class="reference internal" href="#dictionaries" id="id42">Dictionaries</a><ul>
<li><a class="reference internal" href="#how-can-i-get-a-dictionary-to-display-its-keys-in-a-consistent-order" id="id43">How can I get a dictionary to display its keys in a consistent order?</a></li>
<li><a class="reference internal" href="#i-want-to-do-a-complicated-sort-can-you-do-a-schwartzian-transform-in-python" id="id44">I want to do a complicated sort: can you do a Schwartzian Transform in Python?</a></li>
<li><a class="reference internal" href="#how-can-i-sort-one-list-by-values-from-another-list" id="id45">How can I sort one list by values from another list?</a></li>
</ul>
</li>
<li><a class="reference internal" href="#objects" id="id46">Objects</a><ul>
<li><a class="reference internal" href="#what-is-a-class" id="id47">What is a class?</a></li>
<li><a class="reference internal" href="#what-is-a-method" id="id48">What is a method?</a></li>
<li><a class="reference internal" href="#what-is-self" id="id49">What is self?</a></li>
<li><a class="reference internal" href="#how-do-i-check-if-an-object-is-an-instance-of-a-given-class-or-of-a-subclass-of-it" id="id50">How do I check if an object is an instance of a given class or of a subclass of it?</a></li>
<li><a class="reference internal" href="#what-is-delegation" id="id51">What is delegation?</a></li>
<li><a class="reference internal" href="#how-do-i-call-a-method-defined-in-a-base-class-from-a-derived-class-that-overrides-it" id="id52">How do I call a method defined in a base class from a derived class that overrides it?</a></li>
<li><a class="reference internal" href="#how-can-i-organize-my-code-to-make-it-easier-to-change-the-base-class" id="id53">How can I organize my code to make it easier to change the base class?</a></li>
<li><a class="reference internal" href="#how-do-i-create-static-class-data-and-static-class-methods" id="id54">How do I create static class data and static class methods?</a></li>
<li><a class="reference internal" href="#how-can-i-overload-constructors-or-methods-in-python" id="id55">How can I overload constructors (or methods) in Python?</a></li>
<li><a class="reference internal" href="#i-try-to-use-spam-and-i-get-an-error-about-someclassname-spam" id="id56">I try to use __spam and I get an error about _SomeClassName__spam.</a></li>
<li><a class="reference internal" href="#my-class-defines-del-but-it-is-not-called-when-i-delete-the-object" id="id57">My class defines __del__ but it is not called when I delete the object.</a></li>
<li><a class="reference internal" href="#how-do-i-get-a-list-of-all-instances-of-a-given-class" id="id58">How do I get a list of all instances of a given class?</a></li>
</ul>
</li>
<li><a class="reference internal" href="#modules" id="id59">Modules</a><ul>
<li><a class="reference internal" href="#how-do-i-create-a-pyc-file" id="id60">How do I create a .pyc file?</a></li>
<li><a class="reference internal" href="#how-do-i-find-the-current-module-name" id="id61">How do I find the current module name?</a></li>
<li><a class="reference internal" href="#how-can-i-have-modules-that-mutually-import-each-other" id="id62">How can I have modules that mutually import each other?</a></li>
<li><a class="reference internal" href="#import-x-y-z-returns-module-x-how-do-i-get-z" id="id63">__import__(&#8216;x.y.z&#8217;) returns &lt;module &#8216;x&#8217;&gt;; how do I get z?</a></li>
<li><a class="reference internal" href="#when-i-edit-an-imported-module-and-reimport-it-the-changes-don-t-show-up-why-does-this-happen" id="id64">When I edit an imported module and reimport it, the changes don&#8217;t show up. Why does this happen?</a></li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
<div class="section" id="general-questions">
<h2><a class="toc-backref" href="#id2">General Questions</a><a class="headerlink" href="#general-questions" title="Permalink to this headline">¶</a></h2>
<div class="section" id="is-there-a-source-code-level-debugger-with-breakpoints-single-stepping-etc">
<h3><a class="toc-backref" href="#id3">Is there a source code level debugger with breakpoints, single-stepping, etc.?</a><a class="headerlink" href="#is-there-a-source-code-level-debugger-with-breakpoints-single-stepping-etc" title="Permalink to this headline">¶</a></h3>
Yes.
The pdb module is a simple but adequate console-mode debugger for Python. It is
part of the standard Python library, and is <a class="reference internal" href="../library/pdb.html#module-pdb" title="pdb: The Python debugger for interactive interpreters."><tt class="xref py py-mod docutils literal">documented in the Library
Reference Manual</tt></a>. You can also write your own debugger by using the code
for pdb as an example.
The IDLE interactive development environment, which is part of the standard
Python distribution (normally available as Tools/scripts/idle), includes a
graphical debugger. There is documentation for the IDLE debugger at
<a class="reference external" href="http://www.python.org/idle/doc/idle2.html#Debugger">http://www.python.org/idle/doc/idle2.html#Debugger</a>.
PythonWin is a Python IDE that includes a GUI debugger based on pdb. The
Pythonwin debugger colors breakpoints and has quite a few cool features such as
debugging non-Pythonwin programs. Pythonwin is available as part of the <a class="reference external" href="http://sourceforge.net/projects/pywin32/">Python
for Windows Extensions</a> project and
as a part of the ActivePython distribution (see
<a class="reference external" href="http://www.activestate.com/Products/ActivePython/index.html">http://www.activestate.com/Products/ActivePython/index.html</a>).
<a class="reference external" href="http://boa-constructor.sourceforge.net/">Boa Constructor</a> is an IDE and GUI
builder that uses wxWidgets. It offers visual frame creation and manipulation,
an object inspector, many views on the source like object browsers, inheritance
hierarchies, doc string generated html documentation, an advanced debugger,
integrated help, and Zope support.
<a class="reference external" href="http://www.die-offenbachs.de/eric/index.html">Eric</a> is an IDE built on PyQt
and the Scintilla editing component.
Pydb is a version of the standard Python debugger pdb, modified for use with DDD
(Data Display Debugger), a popular graphical debugger front end. Pydb can be
found at <a class="reference external" href="http://bashdb.sourceforge.net/pydb/">http://bashdb.sourceforge.net/pydb/</a> and DDD can be found at
<a class="reference external" href="http://www.gnu.org/software/ddd">http://www.gnu.org/software/ddd</a>.
There are a number of commercial Python IDEs that include graphical debuggers.
They include:
<ul class="simple">
<li>Wing IDE (<a class="reference external" href="http://wingware.com/">http://wingware.com/</a>)</li>
<li>Komodo IDE (<a class="reference external" href="http://www.activestate.com/Products/Komodo">http://www.activestate.com/Products/Komodo</a>)</li>
</ul>
</div>
<div class="section" id="is-there-a-tool-to-help-find-bugs-or-perform-static-analysis">
<h3><a class="toc-backref" href="#id4">Is there a tool to help find bugs or perform static analysis?</a><a class="headerlink" href="#is-there-a-tool-to-help-find-bugs-or-perform-static-analysis" title="Permalink to this headline">¶</a></h3>
Yes.
PyChecker is a static analysis tool that finds bugs in Python source code and
warns about code complexity and style. You can get PyChecker from
<a class="reference external" href="http://pychecker.sf.net">http://pychecker.sf.net</a>.
<a class="reference external" href="http://www.logilab.org/projects/pylint">Pylint</a> is another tool that checks
if a module satisfies a coding standard, and also makes it possible to write
plug-ins to add a custom feature. In addition to the bug checking that
PyChecker performs, Pylint offers some additional features such as checking line
length, whether variable names are well-formed according to your coding
standard, whether declared interfaces are fully implemented, and more.
<a class="reference external" href="http://www.logilab.org/card/pylint_manual">http://www.logilab.org/card/pylint_manual</a> provides a full list of Pylint&#8217;s
features.
</div>
<div class="section" id="how-can-i-create-a-stand-alone-binary-from-a-python-script">
<h3><a class="toc-backref" href="#id5">How can I create a stand-alone binary from a Python script?</a><a class="headerlink" href="#how-can-i-create-a-stand-alone-binary-from-a-python-script" title="Permalink to this headline">¶</a></h3>
You don&#8217;t need the ability to compile Python to C code if all you want is a
stand-alone program that users can download and run without having to install
the Python distribution first. There are a number of tools that determine the
set of modules required by a program and bind these modules together with a
Python binary to produce a single executable.
One is to use the freeze tool, which is included in the Python source tree as
<tt class="docutils literal">Tools/freeze</tt>. It converts Python byte code to C arrays; a C compiler you can
embed all your modules into a new program, which is then linked with the
standard Python modules.
It works by scanning your source recursively for import statements (in both
forms) and looking for the modules in the standard Python path as well as in the
source directory (for built-in modules). It then turns the bytecode for modules
written in Python into C code (array initializers that can be turned into code
objects using the marshal module) and creates a custom-made config file that
only contains those built-in modules which are actually used in the program. It
then compiles the generated C code and links it with the rest of the Python
interpreter to form a self-contained binary which acts exactly like your script.
Obviously, freeze requires a C compiler. There are several other utilities
which don&#8217;t. One is Thomas Heller&#8217;s py2exe (Windows only) at
<blockquote>
<div><a class="reference external" href="http://www.py2exe.org/">http://www.py2exe.org/</a></div></blockquote>
Another is Christian Tismer&#8217;s <a class="reference external" href="http://starship.python.net/crew/pirx">SQFREEZE</a>
which appends the byte code to a specially-prepared Python interpreter that can
find the byte code in the executable.
Other tools include Fredrik Lundh&#8217;s <a class="reference external" href="http://www.pythonware.com/products/python/squeeze">Squeeze</a> and Anthony Tuininga&#8217;s
<a class="reference external" href="http://starship.python.net/crew/atuining/cx_Freeze/index.html">cx_Freeze</a>.
</div>
<div class="section" id="are-there-coding-standards-or-a-style-guide-for-python-programs">
<h3><a class="toc-backref" href="#id6">Are there coding standards or a style guide for Python programs?</a><a class="headerlink" href="#are-there-coding-standards-or-a-style-guide-for-python-programs" title="Permalink to this headline">¶</a></h3>
Yes. The coding style required for standard library modules is documented as
<a class="pep reference external" href="http://www.python.org/dev/peps/pep-0008">PEP 8</a>.
</div>
<div class="section" id="my-program-is-too-slow-how-do-i-speed-it-up">
<h3><a class="toc-backref" href="#id7">My program is too slow. How do I speed it up?</a><a class="headerlink" href="#my-program-is-too-slow-how-do-i-speed-it-up" title="Permalink to this headline">¶</a></h3>
That&#8217;s a tough one, in general. There are many tricks to speed up Python code;
consider rewriting parts in C as a last resort.
In some cases it&#8217;s possible to automatically translate Python to C or x86
assembly language, meaning that you don&#8217;t have to modify your code to gain
increased speed.
<a class="reference external" href="http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/">Pyrex</a> can compile a
slightly modified version of Python code into a C extension, and can be used on
many different platforms.
<a class="reference external" href="http://psyco.sourceforge.net">Psyco</a> is a just-in-time compiler that
translates Python code into x86 assembly language. If you can use it, Psyco can
provide dramatic speedups for critical functions.
The rest of this answer will discuss various tricks for squeezing a bit more
speed out of Python code. Never apply any optimization tricks unless you know
you need them, after profiling has indicated that a particular function is the
heavily executed hot spot in the code. Optimizations almost always make the
code less clear, and you shouldn&#8217;t pay the costs of reduced clarity (increased
development time, greater likelihood of bugs) unless the resulting performance
benefit is worth it.
There is a page on the wiki devoted to <a class="reference external" href="http://wiki.python.org/moin/PythonSpeed/PerformanceTips">performance tips</a>.
Guido van Rossum has written up an anecdote related to optimization at
<a class="reference external" href="http://www.python.org/doc/essays/list2str.html">http://www.python.org/doc/essays/list2str.html</a>.
One thing to notice is that function and (especially) method calls are rather
expensive; if you have designed a purely OO interface with lots of tiny
functions that don&#8217;t do much more than get or set an instance variable or call
another method, you might consider using a more direct way such as directly
accessing instance variables. Also see the standard module <a class="reference internal" href="../library/profile.html#module-profile" title="profile: Python source profiler."><tt class="xref py py-mod docutils literal">profile</tt></a> which
makes it possible to find out where your program is spending most of its time
(if you have some patience &#8211; the profiling itself can slow your program down by
an order of magnitude).
Remember that many standard optimization heuristics you may know from other
programming experience may well apply to Python. For example it may be faster
to send output to output devices using larger writes rather than smaller ones in
order to reduce the overhead of kernel system calls. Thus CGI scripts that
write all output in &#8220;one shot&#8221; may be faster than those that write lots of small
pieces of output.
Also, be sure to use Python&#8217;s core features where appropriate. For example,
slicing allows programs to chop up lists and other sequence objects in a single
tick of the interpreter&#8217;s mainloop using highly optimized C implementations.
Thus to get the same effect as:
<div class="highlight-python"><div class="highlight"><pre>L2 = []
for i in range(3):
 L2.append(L1[i])
</pre></div>
</div>
it is much shorter and far faster to use
<div class="highlight-python"><div class="highlight"><pre>L2 = list(L1[:3]) # &quot;list&quot; is redundant if L1 is a list.
</pre></div>
</div>
Note that the functionally-oriented built-in functions such as <a class="reference internal" href="../library/functions.html#map" title="map"><tt class="xref py py-func docutils literal">map()</tt></a>,
<a class="reference internal" href="../library/functions.html#zip" title="zip"><tt class="xref py py-func docutils literal">zip()</tt></a>, and friends can be a convenient accelerator for loops that
perform a single task. For example to pair the elements of two lists
together:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; zip([1, 2, 3], [4, 5, 6])
[(1, 4), (2, 5), (3, 6)]
</pre></div>
</div>
or to compute a number of sines:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; map(math.sin, (1, 2, 3, 4))
[0.841470984808, 0.909297426826, 0.14112000806, -0.756802495308]
</pre></div>
</div>
The operation completes very quickly in such cases.
Other examples include the <tt class="docutils literal">join()</tt> and <tt class="docutils literal">split()</tt> <a class="reference internal" href="../library/stdtypes.html#string-methods">methods
of string objects</a>.
For example if s1..s7 are large (10K+) strings then
<tt class="docutils literal">&quot;&quot;.join([s1,s2,s3,s4,s5,s6,s7])</tt> may be far faster than the more obvious
<tt class="docutils literal">s1+s2+s3+s4+s5+s6+s7</tt>, since the &#8220;summation&#8221; will compute many
subexpressions, whereas <tt class="docutils literal">join()</tt> does all the copying in one pass. For
manipulating strings, use the <tt class="docutils literal">replace()</tt> and the <tt class="docutils literal">format()</tt> <a class="reference internal" href="../library/stdtypes.html#string-methods">methods
on string objects</a>. Use regular expressions only when you&#8217;re
not dealing with constant string patterns. You may still use <a class="reference internal" href="../library/stdtypes.html#string-formatting">the old %
operations</a> <tt class="docutils literal">string % tuple</tt> and <tt class="docutils literal">string % dictionary</tt>.
Be sure to use the <tt class="xref py py-meth docutils literal">list.sort()</tt> built-in method to do sorting, and see the
<a class="reference external" href="http://wiki.python.org/moin/HowTo/Sorting">sorting mini-HOWTO</a> for examples
of moderately advanced usage. <tt class="xref py py-meth docutils literal">list.sort()</tt> beats other techniques for
sorting in all but the most extreme circumstances.
Another common trick is to &#8220;push loops into functions or methods.&#8221; For example
suppose you have a program that runs slowly and you use the profiler to
determine that a Python function <tt class="docutils literal">ff()</tt> is being called lots of times. If you
notice that <tt class="docutils literal">ff()</tt>:
<div class="highlight-python"><div class="highlight"><pre>def ff(x):
 ... # do something with x computing result...
 return result
</pre></div>
</div>
tends to be called in loops like:
<div class="highlight-python"><div class="highlight"><pre>list = map(ff, oldlist)
</pre></div>
</div>
or:
<div class="highlight-python"><div class="highlight"><pre>for x in sequence:
 value = ff(x)
 ... # do something with value...
</pre></div>
</div>
then you can often eliminate function call overhead by rewriting <tt class="docutils literal">ff()</tt> to:
<div class="highlight-python"><div class="highlight"><pre>def ffseq(seq):
 resultseq = []
 for x in seq:
 ... # do something with x computing result...
 resultseq.append(result)
 return resultseq
</pre></div>
</div>
and rewrite the two examples to <tt class="docutils literal">list = ffseq(oldlist)</tt> and to:
<div class="highlight-python"><div class="highlight"><pre>for value in ffseq(sequence):
 ... # do something with value...
</pre></div>
</div>
Single calls to <tt class="docutils literal">ff(x)</tt> translate to <tt class="docutils literal">ffseq([x])[0]</tt> with little penalty.
Of course this technique is not always appropriate and there are other variants
which you can figure out.
You can gain some performance by explicitly storing the results of a function or
method lookup into a local variable. A loop like:
<div class="highlight-python"><div class="highlight"><pre>for key in token:
 dict[key] = dict.get(key, 0) + 1
</pre></div>
</div>
resolves <tt class="docutils literal">dict.get</tt> every iteration. If the method isn&#8217;t going to change, a
slightly faster implementation is:
<div class="highlight-python"><div class="highlight"><pre>dict_get = dict.get # look up the method once
for key in token:
 dict[key] = dict_get(key, 0) + 1
</pre></div>
</div>
Default arguments can be used to determine values once, at compile time instead
of at run time. This can only be done for functions or objects which will not
be changed during program execution, such as replacing
<div class="highlight-python"><div class="highlight"><pre>def degree_sin(deg):
 return math.sin(deg * math.pi / 180.0)
</pre></div>
</div>
with
<div class="highlight-python"><div class="highlight"><pre>def degree_sin(deg, factor=math.pi/180.0, sin=math.sin):
 return sin(deg * factor)
</pre></div>
</div>
Because this trick uses default arguments for terms which should not be changed,
it should only be used when you are not concerned with presenting a possibly
confusing API to your users.
</div>
</div>
<div class="section" id="core-language">
<h2><a class="toc-backref" href="#id8">Core Language</a><a class="headerlink" href="#core-language" title="Permalink to this headline">¶</a></h2>
<div class="section" id="why-am-i-getting-an-unboundlocalerror-when-the-variable-has-a-value">
<h3><a class="toc-backref" href="#id9">Why am I getting an UnboundLocalError when the variable has a value?</a><a class="headerlink" href="#why-am-i-getting-an-unboundlocalerror-when-the-variable-has-a-value" title="Permalink to this headline">¶</a></h3>
It can be a surprise to get the UnboundLocalError in previously working
code when it is modified by adding an assignment statement somewhere in
the body of a function.
This code:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; x = 10
&gt;&gt;&gt; def bar():
... print x
&gt;&gt;&gt; bar()
10
</pre></div>
</div>
works, but this code:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; x = 10
&gt;&gt;&gt; def foo():
... print x
... x += 1
</pre></div>
</div>
results in an UnboundLocalError:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; foo()
Traceback (most recent call last):
 ...
UnboundLocalError: local variable &#39;x&#39; referenced before assignment
</pre></div>
</div>
This is because when you make an assignment to a variable in a scope, that
variable becomes local to that scope and shadows any similarly named variable
in the outer scope. Since the last statement in foo assigns a new value to
<tt class="docutils literal">x</tt>, the compiler recognizes it as a local variable. Consequently when the
earlier <tt class="docutils literal">print x</tt> attempts to print the uninitialized local variable and
an error results.
In the example above you can access the outer scope variable by declaring it
global:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; x = 10
&gt;&gt;&gt; def foobar():
... global x
... print x
... x += 1
&gt;&gt;&gt; foobar()
10
</pre></div>
</div>
This explicit declaration is required in order to remind you that (unlike the
superficially analogous situation with class and instance variables) you are
actually modifying the value of the variable in the outer scope:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; print x
11
</pre></div>
</div>
</div>
<div class="section" id="what-are-the-rules-for-local-and-global-variables-in-python">
<h3><a class="toc-backref" href="#id10">What are the rules for local and global variables in Python?</a><a class="headerlink" href="#what-are-the-rules-for-local-and-global-variables-in-python" title="Permalink to this headline">¶</a></h3>
In Python, variables that are only referenced inside a function are implicitly
global. If a variable is assigned a new value anywhere within the function&#8217;s
body, it&#8217;s assumed to be a local. If a variable is ever assigned a new value
inside the function, the variable is implicitly local, and you need to
explicitly declare it as &#8216;global&#8217;.
Though a bit surprising at first, a moment&#8217;s consideration explains this. On
one hand, requiring <a class="reference internal" href="../reference/simple_stmts.html#global"><tt class="xref std std-keyword docutils literal">global</tt></a> for assigned variables provides a bar
against unintended side-effects. On the other hand, if <tt class="docutils literal">global</tt> was required
for all global references, you&#8217;d be using <tt class="docutils literal">global</tt> all the time. You&#8217;d have
to declare as global every reference to a built-in function or to a component of
an imported module. This clutter would defeat the usefulness of the <tt class="docutils literal">global</tt>
declaration for identifying side-effects.
</div>
<div class="section" id="why-do-lambdas-defined-in-a-loop-with-different-values-all-return-the-same-result">
<h3><a class="toc-backref" href="#id11">Why do lambdas defined in a loop with different values all return the same result?</a><a class="headerlink" href="#why-do-lambdas-defined-in-a-loop-with-different-values-all-return-the-same-result" title="Permalink to this headline">¶</a></h3>
Assume you use a for loop to define a few different lambdas (or even plain
functions), e.g.:
<div class="highlight-python"><div class="highlight"><pre>squares = []
for x in range(5):
 squares.append(lambda: x**2)
</pre></div>
</div>
This gives you a list that contains 5 lambdas that calculate <tt class="docutils literal">x**2</tt>. You
might expect that, when called, they would return, respectively, <tt class="docutils literal">0</tt>, <tt class="docutils literal">1</tt>,
<tt class="docutils literal">4</tt>, <tt class="docutils literal">9</tt>, and <tt class="docutils literal">16</tt>. However, when you actually try you will see that
they all return <tt class="docutils literal">16</tt>:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; squares[2]()
16
&gt;&gt;&gt; squares[4]()
16
</pre></div>
</div>
This happens because <tt class="docutils literal">x</tt> is not local to the lambdas, but is defined in
the outer scope, and it is accessed when the lambda is called &#8212; not when it
is defined. At the end of the loop, the value of <tt class="docutils literal">x</tt> is <tt class="docutils literal">4</tt>, so all the
functions now return <tt class="docutils literal">4**2</tt>, i.e. <tt class="docutils literal">16</tt>. You can also verify this by
changing the value of <tt class="docutils literal">x</tt> and see how the results of the lambdas change:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; x = 8
&gt;&gt;&gt; squares[2]()
64
</pre></div>
</div>
In order to avoid this, you need to save the values in variables local to the
lambdas, so that they don&#8217;t rely on the value of the global <tt class="docutils literal">x</tt>:
<div class="highlight-python"><div class="highlight"><pre>squares = []
for x in range(5):
 squares.append(lambda n=x: n**2)
</pre></div>
</div>
Here, <tt class="docutils literal">n=x</tt> creates a new variable <tt class="docutils literal">n</tt> local to the lambda and computed
when the lambda is defined so that it has the same value that <tt class="docutils literal">x</tt> had at
that point in the loop. This means that the value of <tt class="docutils literal">n</tt> will be <tt class="docutils literal">0</tt>
in the first lambda, <tt class="docutils literal">1</tt> in the second, <tt class="docutils literal">2</tt> in the third, and so on.
Therefore each lambda will now return the correct result:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; squares[2]()
4
&gt;&gt;&gt; squares[4]()
16
</pre></div>
</div>
Note that this behaviour is not peculiar to lambdas, but applies to regular
functions too.
</div>
<div class="section" id="how-do-i-share-global-variables-across-modules">
<h3><a class="toc-backref" href="#id12">How do I share global variables across modules?</a><a class="headerlink" href="#how-do-i-share-global-variables-across-modules" title="Permalink to this headline">¶</a></h3>
The canonical way to share information across modules within a single program is
to create a special module (often called config or cfg). Just import the config
module in all modules of your application; the module then becomes available as
a global name. Because there is only one instance of each module, any changes
made to the module object get reflected everywhere. For example:
config.py:
<div class="highlight-python"><div class="highlight"><pre>x = 0 # Default value of the &#39;x&#39; configuration setting
</pre></div>
</div>
mod.py:
<div class="highlight-python"><div class="highlight"><pre>import config
config.x = 1
</pre></div>
</div>
main.py:
<div class="highlight-python"><div class="highlight"><pre>import config
import mod
print config.x
</pre></div>
</div>
Note that using a module is also the basis for implementing the Singleton design
pattern, for the same reason.
</div>
<div class="section" id="what-are-the-best-practices-for-using-import-in-a-module">
<h3><a class="toc-backref" href="#id13">What are the &#8220;best practices&#8221; for using import in a module?</a><a class="headerlink" href="#what-are-the-best-practices-for-using-import-in-a-module" title="Permalink to this headline">¶</a></h3>
In general, don&#8217;t use <tt class="docutils literal">from modulename import *</tt>. Doing so clutters the
importer&#8217;s namespace. Some people avoid this idiom even with the few modules
that were designed to be imported in this manner. Modules designed in this
manner include <a class="reference internal" href="../library/tkinter.html#module-Tkinter" title="Tkinter: Interface to Tcl/Tk for graphical user interfaces"><tt class="xref py py-mod docutils literal">Tkinter</tt></a>, and <a class="reference internal" href="../library/threading.html#module-threading" title="threading: Higher-level threading interface."><tt class="xref py py-mod docutils literal">threading</tt></a>.
Import modules at the top of a file. Doing so makes it clear what other modules
your code requires and avoids questions of whether the module name is in scope.
Using one import per line makes it easy to add and delete module imports, but
using multiple imports per line uses less screen space.
It&#8217;s good practice if you import modules in the following order:
<ol class="arabic simple">
<li>standard library modules &#8211; e.g. <tt class="docutils literal">sys</tt>, <tt class="docutils literal">os</tt>, <tt class="docutils literal">getopt</tt>, <tt class="docutils literal">re</tt></li>
<li>third-party library modules (anything installed in Python&#8217;s site-packages
directory) &#8211; e.g. mx.DateTime, ZODB, PIL.Image, etc.</li>
<li>locally-developed modules</li>
</ol>
Never use relative package imports. If you&#8217;re writing code that&#8217;s in the
<tt class="docutils literal">package.sub.m1</tt> module and want to import <tt class="docutils literal">package.sub.m2</tt>, do not just
write <tt class="docutils literal">import m2</tt>, even though it&#8217;s legal. Write <tt class="docutils literal">from package.sub import
m2</tt> instead. Relative imports can lead to a module being initialized twice,
leading to confusing bugs. See <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0328">PEP 328</a> for details.
It is sometimes necessary to move imports to a function or class to avoid
problems with circular imports. Gordon McMillan says:
<blockquote>
<div>Circular imports are fine where both modules use the &#8220;import &lt;module&gt;&#8221; form
of import. They fail when the 2nd module wants to grab a name out of the
first (&#8220;from module import name&#8221;) and the import is at the top level. That&#8217;s
because names in the 1st are not yet available, because the first module is
busy importing the 2nd.</div></blockquote>
In this case, if the second module is only used in one function, then the import
can easily be moved into that function. By the time the import is called, the
first module will have finished initializing, and the second module can do its
import.
It may also be necessary to move imports out of the top level of code if some of
the modules are platform-specific. In that case, it may not even be possible to
import all of the modules at the top of the file. In this case, importing the
correct modules in the corresponding platform-specific code is a good option.
Only move imports into a local scope, such as inside a function definition, if
it&#8217;s necessary to solve a problem such as avoiding a circular import or are
trying to reduce the initialization time of a module. This technique is
especially helpful if many of the imports are unnecessary depending on how the
program executes. You may also want to move imports into a function if the
modules are only ever used in that function. Note that loading a module the
first time may be expensive because of the one time initialization of the
module, but loading a module multiple times is virtually free, costing only a
couple of dictionary lookups. Even if the module name has gone out of scope,
the module is probably available in <a class="reference internal" href="../library/sys.html#sys.modules" title="sys.modules"><tt class="xref py py-data docutils literal">sys.modules</tt></a>.
If only instances of a specific class use a module, then it is reasonable to
import the module in the class&#8217;s <tt class="docutils literal">__init__</tt> method and then assign the module
to an instance variable so that the module is always available (via that
instance variable) during the life of the object. Note that to delay an import
until the class is instantiated, the import must be inside a method. Putting
the import inside the class but outside of any method still causes the import to
occur when the module is initialized.
</div>
<div class="section" id="how-can-i-pass-optional-or-keyword-parameters-from-one-function-to-another">
<h3><a class="toc-backref" href="#id14">How can I pass optional or keyword parameters from one function to another?</a><a class="headerlink" href="#how-can-i-pass-optional-or-keyword-parameters-from-one-function-to-another" title="Permalink to this headline">¶</a></h3>
Collect the arguments using the <tt class="docutils literal">*</tt> and <tt class="docutils literal">**</tt> specifiers in the function&#8217;s
parameter list; this gives you the positional arguments as a tuple and the
keyword arguments as a dictionary. You can then pass these arguments when
calling another function by using <tt class="docutils literal">*</tt> and <tt class="docutils literal">**</tt>:
<div class="highlight-python"><div class="highlight"><pre>def f(x, *args, **kwargs):
 ...
 kwargs[&#39;width&#39;] = &#39;14.3c&#39;
 ...
 g(x, *args, **kwargs)
</pre></div>
</div>
In the unlikely case that you care about Python versions older than 2.0, use
<a class="reference internal" href="../library/functions.html#apply" title="apply"><tt class="xref py py-func docutils literal">apply()</tt></a>:
<div class="highlight-python"><div class="highlight"><pre>def f(x, *args, **kwargs):
 ...
 kwargs[&#39;width&#39;] = &#39;14.3c&#39;
 ...
 apply(g, (x,)+args, kwargs)
</pre></div>
</div>
</div>
<div class="section" id="what-is-the-difference-between-arguments-and-parameters">
<h3><a class="toc-backref" href="#id15">What is the difference between arguments and parameters?</a><a class="headerlink" href="#what-is-the-difference-between-arguments-and-parameters" title="Permalink to this headline">¶</a></h3>
<a class="reference internal" href="../glossary.html#term-parameter">Parameters</a> are defined by the names that appear in a
function definition, whereas <a class="reference internal" href="../glossary.html#term-argument">arguments</a> are the values
actually passed to a function when calling it. Parameters define what types of
arguments a function can accept. For example, given the function definition:
<div class="highlight-python"><div class="highlight"><pre>def func(foo, bar=None, **kwargs):
 pass
</pre></div>
</div>
foo, bar and kwargs are parameters of <tt class="docutils literal">func</tt>. However, when calling
<tt class="docutils literal">func</tt>, for example:
<div class="highlight-python"><div class="highlight"><pre>func(42, bar=314, extra=somevar)
</pre></div>
</div>
the values <tt class="docutils literal">42</tt>, <tt class="docutils literal">314</tt>, and <tt class="docutils literal">somevar</tt> are arguments.
</div>
<div class="section" id="how-do-i-write-a-function-with-output-parameters-call-by-reference">
<h3><a class="toc-backref" href="#id16">How do I write a function with output parameters (call by reference)?</a><a class="headerlink" href="#how-do-i-write-a-function-with-output-parameters-call-by-reference" title="Permalink to this headline">¶</a></h3>
Remember that arguments are passed by assignment in Python. Since assignment
just creates references to objects, there&#8217;s no alias between an argument name in
the caller and callee, and so no call-by-reference per se. You can achieve the
desired effect in a number of ways.
<ol class="arabic">
<li>By returning a tuple of the results:
<div class="highlight-python"><div class="highlight"><pre>def func2(a, b):
 a = &#39;new-value&#39; # a and b are local names
 b = b + 1 # assigned to new objects
 return a, b # return new values

x, y = &#39;old-value&#39;, 99
x, y = func2(x, y)
print x, y # output: new-value 100
</pre></div>
</div>
This is almost always the clearest solution.
</li>
<li>By using global variables. This isn&#8217;t thread-safe, and is not recommended.
</li>
<li>By passing a mutable (changeable in-place) object:
<div class="highlight-python"><div class="highlight"><pre>def func1(a):
 a[0] = &#39;new-value&#39; # &#39;a&#39; references a mutable list
 a[1] = a[1] + 1 # changes a shared object

args = [&#39;old-value&#39;, 99]
func1(args)
print args[0], args[1] # output: new-value 100
</pre></div>
</div>
</li>
<li>By passing in a dictionary that gets mutated:
<div class="highlight-python"><div class="highlight"><pre>def func3(args):
 args[&#39;a&#39;] = &#39;new-value&#39; # args is a mutable dictionary
 args[&#39;b&#39;] = args[&#39;b&#39;] + 1 # change it in-place

args = {&#39;a&#39;:&#39; old-value&#39;, &#39;b&#39;: 99}
func3(args)
print args[&#39;a&#39;], args[&#39;b&#39;]
</pre></div>
</div>
</li>
<li>Or bundle up values in a class instance:
<div class="highlight-python"><div class="highlight"><pre>class callByRef:
 def __init__(self, **args):
 for (key, value) in args.items():
 setattr(self, key, value)

def func4(args):
 args.a = &#39;new-value&#39; # args is a mutable callByRef
 args.b = args.b + 1 # change object in-place

args = callByRef(a=&#39;old-value&#39;, b=99)
func4(args)
print args.a, args.b
</pre></div>
</div>
There&#8217;s almost never a good reason to get this complicated.
</li>
</ol>
Your best choice is to return a tuple containing the multiple results.
</div>
<div class="section" id="how-do-you-make-a-higher-order-function-in-python">
<h3><a class="toc-backref" href="#id17">How do you make a higher order function in Python?</a><a class="headerlink" href="#how-do-you-make-a-higher-order-function-in-python" title="Permalink to this headline">¶</a></h3>
You have two choices: you can use nested scopes or you can use callable objects.
For example, suppose you wanted to define <tt class="docutils literal">linear(a,b)</tt> which returns a
function <tt class="docutils literal">f(x)</tt> that computes the value <tt class="docutils literal">a*x+b</tt>. Using nested scopes:
<div class="highlight-python"><div class="highlight"><pre>def linear(a, b):
 def result(x):
 return a * x + b
 return result
</pre></div>
</div>
Or using a callable object:
<div class="highlight-python"><div class="highlight"><pre>class linear:

def __init__(self, a, b):
 self.a, self.b = a, b

def __call__(self, x):
 return self.a * x + self.b
</pre></div>
</div>
In both cases,
<div class="highlight-python"><div class="highlight"><pre>taxes = linear(0.3, 2)
</pre></div>
</div>
gives a callable object where <tt class="docutils literal">taxes(10e6) == 0.3 * 10e6 + 2</tt>.
The callable object approach has the disadvantage that it is a bit slower and
results in slightly longer code. However, note that a collection of callables
can share their signature via inheritance:
<div class="highlight-python"><div class="highlight"><pre>class exponential(linear):
 # __init__ inherited
 def __call__(self, x):
 return self.a * (x ** self.b)
</pre></div>
</div>
Object can encapsulate state for several methods:
<div class="highlight-python"><div class="highlight"><pre>class counter:

value = 0

def set(self, x):
 self.value = x

def up(self):
 self.value = self.value + 1

def down(self):
 self.value = self.value - 1

count = counter()
inc, dec, reset = count.up, count.down, count.set
</pre></div>
</div>
Here <tt class="docutils literal">inc()</tt>, <tt class="docutils literal">dec()</tt> and <tt class="docutils literal">reset()</tt> act like functions which share the
same counting variable.
</div>
<div class="section" id="how-do-i-copy-an-object-in-python">
<h3><a class="toc-backref" href="#id18">How do I copy an object in Python?</a><a class="headerlink" href="#how-do-i-copy-an-object-in-python" title="Permalink to this headline">¶</a></h3>
In general, try <a class="reference internal" href="../library/copy.html#copy.copy" title="copy.copy"><tt class="xref py py-func docutils literal">copy.copy()</tt></a> or <a class="reference internal" href="../library/copy.html#copy.deepcopy" title="copy.deepcopy"><tt class="xref py py-func docutils literal">copy.deepcopy()</tt></a> for the general case.
Not all objects can be copied, but most can.
Some objects can be copied more easily. Dictionaries have a <a class="reference internal" href="../library/stdtypes.html#dict.copy" title="dict.copy"><tt class="xref py py-meth docutils literal">copy()</tt></a>
method:
<div class="highlight-python"><div class="highlight"><pre>newdict = olddict.copy()
</pre></div>
</div>
Sequences can be copied by slicing:
<div class="highlight-python"><div class="highlight"><pre>new_l = l[:]
</pre></div>
</div>
</div>
<div class="section" id="how-can-i-find-the-methods-or-attributes-of-an-object">
<h3><a class="toc-backref" href="#id19">How can I find the methods or attributes of an object?</a><a class="headerlink" href="#how-can-i-find-the-methods-or-attributes-of-an-object" title="Permalink to this headline">¶</a></h3>
For an instance x of a user-defined class, <tt class="docutils literal">dir(x)</tt> returns an alphabetized
list of the names containing the instance attributes and methods and attributes
defined by its class.
</div>
<div class="section" id="how-can-my-code-discover-the-name-of-an-object">
<h3><a class="toc-backref" href="#id20">How can my code discover the name of an object?</a><a class="headerlink" href="#how-can-my-code-discover-the-name-of-an-object" title="Permalink to this headline">¶</a></h3>
Generally speaking, it can&#8217;t, because objects don&#8217;t really have names.
Essentially, assignment always binds a name to a value; The same is true of
<tt class="docutils literal">def</tt> and <tt class="docutils literal">class</tt> statements, but in that case the value is a
callable. Consider the following code:
<div class="highlight-python"><pre>class A:
 pass

B = A

a = B()
b = a
print b
&lt;__main__.A instance at 0x16D07CC&gt;
print a
&lt;__main__.A instance at 0x16D07CC&gt;</pre>
</div>
Arguably the class has a name: even though it is bound to two names and invoked
through the name B the created instance is still reported as an instance of
class A. However, it is impossible to say whether the instance&#8217;s name is a or
b, since both names are bound to the same value.
Generally speaking it should not be necessary for your code to &#8220;know the names&#8221;
of particular values. Unless you are deliberately writing introspective
programs, this is usually an indication that a change of approach might be
beneficial.
In comp.lang.python, Fredrik Lundh once gave an excellent analogy in answer to
this question:
<blockquote>
<div>The same way as you get the name of that cat you found on your porch: the cat
(object) itself cannot tell you its name, and it doesn&#8217;t really care &#8211; so
the only way to find out what it&#8217;s called is to ask all your neighbours
(namespaces) if it&#8217;s their cat (object)...
....and don&#8217;t be surprised if you&#8217;ll find that it&#8217;s known by many names, or
no name at all!
</div></blockquote>
</div>
<div class="section" id="what-s-up-with-the-comma-operator-s-precedence">
<h3><a class="toc-backref" href="#id21">What&#8217;s up with the comma operator&#8217;s precedence?</a><a class="headerlink" href="#what-s-up-with-the-comma-operator-s-precedence" title="Permalink to this headline">¶</a></h3>
Comma is not an operator in Python. Consider this session:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; &quot;a&quot; in &quot;b&quot;, &quot;a&quot;
(False, &#39;a&#39;)
</pre></div>
</div>
Since the comma is not an operator, but a separator between expressions the
above is evaluated as if you had entered:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; (&quot;a&quot; in &quot;b&quot;), &quot;a&quot;
</pre></div>
</div>
not:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; &quot;a&quot; in (&quot;b&quot;, &quot;a&quot;)
</pre></div>
</div>
The same is true of the various assignment operators (<tt class="docutils literal">=</tt>, <tt class="docutils literal">+=</tt> etc). They
are not truly operators but syntactic delimiters in assignment statements.
</div>
<div class="section" id="is-there-an-equivalent-of-c-s-ternary-operator">
<h3><a class="toc-backref" href="#id22">Is there an equivalent of C&#8217;s &#8221;?:&#8221; ternary operator?</a><a class="headerlink" href="#is-there-an-equivalent-of-c-s-ternary-operator" title="Permalink to this headline">¶</a></h3>
Yes, this feature was added in Python 2.5. The syntax would be as follows:
<div class="highlight-python"><div class="highlight"><pre>[on_true] if [expression] else [on_false]

x, y = 50, 25

small = x if x &lt; y else y
</pre></div>
</div>
For versions previous to 2.5 the answer would be &#8216;No&#8217;.
</div>
<div class="section" id="is-it-possible-to-write-obfuscated-one-liners-in-python">
<h3><a class="toc-backref" href="#id23">Is it possible to write obfuscated one-liners in Python?</a><a class="headerlink" href="#is-it-possible-to-write-obfuscated-one-liners-in-python" title="Permalink to this headline">¶</a></h3>
Yes. Usually this is done by nesting <a class="reference internal" href="../reference/expressions.html#lambda"><tt class="xref std std-keyword docutils literal">lambda</tt></a> within
<a class="reference internal" href="../reference/expressions.html#lambda"><tt class="xref std std-keyword docutils literal">lambda</tt></a>. See the following three examples, due to Ulf Bartelt:
<div class="highlight-python"><div class="highlight"><pre># Primes &lt; 1000
print filter(None,map(lambda y:y*reduce(lambda x,y:x*y!=0,
map(lambda x,y=y:y%x,range(2,int(pow(y,0.5)+1))),1),range(2,1000)))

# First 10 Fibonacci numbers
print map(lambda x,f=lambda x,f:(f(x-1,f)+f(x-2,f)) if x&gt;1 else 1: f(x,f),
range(10))

# Mandelbrot set
print (lambda Ru,Ro,Iu,Io,IM,Sx,Sy:reduce(lambda x,y:x+y,map(lambda y,
Iu=Iu,Io=Io,Ru=Ru,Ro=Ro,Sy=Sy,L=lambda yc,Iu=Iu,Io=Io,Ru=Ru,Ro=Ro,i=IM,
Sx=Sx,Sy=Sy:reduce(lambda x,y:x+y,map(lambda x,xc=Ru,yc=yc,Ru=Ru,Ro=Ro,
i=i,Sx=Sx,F=lambda xc,yc,x,y,k,f=lambda xc,yc,x,y,k,f:(k&lt;=0)or (x*x+y*y
&gt;=4.0) or 1+f(xc,yc,x*x-y*y+xc,2.0*x*y+yc,k-1,f):f(xc,yc,x,y,k,f):chr(
64+F(Ru+x*(Ro-Ru)/Sx,yc,0,0,i)),range(Sx))):L(Iu+y*(Io-Iu)/Sy),range(Sy
))))(-2.1, 0.7, -1.2, 1.2, 30, 80, 24)
# \___ ___/ \___ ___/ | | |__ lines on screen
# V V | |______ columns on screen
# | | |__________ maximum of &quot;iterations&quot;
# | |_________________ range on y axis
# |____________________________ range on x axis
</pre></div>
</div>
Don&#8217;t try this at home, kids!
</div>
</div>
<div class="section" id="numbers-and-strings">
<h2><a class="toc-backref" href="#id24">Numbers and strings</a><a class="headerlink" href="#numbers-and-strings" title="Permalink to this headline">¶</a></h2>
<div class="section" id="how-do-i-specify-hexadecimal-and-octal-integers">
<h3><a class="toc-backref" href="#id25">How do I specify hexadecimal and octal integers?</a><a class="headerlink" href="#how-do-i-specify-hexadecimal-and-octal-integers" title="Permalink to this headline">¶</a></h3>
To specify an octal digit, precede the octal value with a zero, and then a lower
or uppercase &#8220;o&#8221;. For example, to set the variable &#8220;a&#8221; to the octal value &#8220;10&#8221;
(8 in decimal), type:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; a = 0o10
&gt;&gt;&gt; a
8
</pre></div>
</div>
Hexadecimal is just as easy. Simply precede the hexadecimal number with a zero,
and then a lower or uppercase &#8220;x&#8221;. Hexadecimal digits can be specified in lower
or uppercase. For example, in the Python interpreter:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; a = 0xa5
&gt;&gt;&gt; a
165
&gt;&gt;&gt; b = 0XB2
&gt;&gt;&gt; b
178
</pre></div>
</div>
</div>
<div class="section" id="why-does-22-10-return-3">
<h3><a class="toc-backref" href="#id26">Why does -22 // 10 return -3?</a><a class="headerlink" href="#why-does-22-10-return-3" title="Permalink to this headline">¶</a></h3>
It&#8217;s primarily driven by the desire that <tt class="docutils literal">i % j</tt> have the same sign as <tt class="docutils literal">j</tt>.
If you want that, and also want:
<div class="highlight-python"><div class="highlight"><pre>i == (i // j) * j + (i % j)
</pre></div>
</div>
then integer division has to return the floor. C also requires that identity to
hold, and then compilers that truncate <tt class="docutils literal">i // j</tt> need to make <tt class="docutils literal">i % j</tt> have
the same sign as <tt class="docutils literal">i</tt>.
There are few real use cases for <tt class="docutils literal">i % j</tt> when <tt class="docutils literal">j</tt> is negative. When <tt class="docutils literal">j</tt>
is positive, there are many, and in virtually all of them it&#8217;s more useful for
<tt class="docutils literal">i % j</tt> to be <tt class="docutils literal">&gt;= 0</tt>. If the clock says 10 now, what did it say 200 hours
ago? <tt class="docutils literal">-190 % 12 == 2</tt> is useful; <tt class="docutils literal">-190 % 12 == -10</tt> is a bug waiting to
bite.
<div class="admonition note">
Note
On Python 2, <tt class="docutils literal">a / b</tt> returns the same as <tt class="docutils literal">a // b</tt> if
<tt class="docutils literal">__future__.division</tt> is not in effect. This is also known as &#8220;classic&#8221;
division.
</div>
</div>
<div class="section" id="how-do-i-convert-a-string-to-a-number">
<h3><a class="toc-backref" href="#id27">How do I convert a string to a number?</a><a class="headerlink" href="#how-do-i-convert-a-string-to-a-number" title="Permalink to this headline">¶</a></h3>
For integers, use the built-in <a class="reference internal" href="../library/functions.html#int" title="int"><tt class="xref py py-func docutils literal">int()</tt></a> type constructor, e.g. <tt class="docutils literal">int('144')
== 144</tt>. Similarly, <a class="reference internal" href="../library/functions.html#float" title="float"><tt class="xref py py-func docutils literal">float()</tt></a> converts to floating-point,
e.g. <tt class="docutils literal">float('144') == 144.0</tt>.
By default, these interpret the number as decimal, so that <tt class="docutils literal">int('0144') ==
144</tt> and <tt class="docutils literal">int('0x144')</tt> raises <a class="reference internal" href="../library/exceptions.html#exceptions.ValueError" title="exceptions.ValueError"><tt class="xref py py-exc docutils literal">ValueError</tt></a>. <tt class="docutils literal">int(string, base)</tt> takes
the base to convert from as a second optional argument, so <tt class="docutils literal">int('0x144', 16) ==
324</tt>. If the base is specified as 0, the number is interpreted using Python&#8217;s
rules: a leading &#8216;0&#8217; indicates octal, and &#8216;0x&#8217; indicates a hex number.
Do not use the built-in function <a class="reference internal" href="../library/functions.html#eval" title="eval"><tt class="xref py py-func docutils literal">eval()</tt></a> if all you need is to convert
strings to numbers. <a class="reference internal" href="../library/functions.html#eval" title="eval"><tt class="xref py py-func docutils literal">eval()</tt></a> will be significantly slower and it presents a
security risk: someone could pass you a Python expression that might have
unwanted side effects. For example, someone could pass
<tt class="docutils literal">__import__('os').system(&quot;rm -rf $HOME&quot;)</tt> which would erase your home
directory.
<a class="reference internal" href="../library/functions.html#eval" title="eval"><tt class="xref py py-func docutils literal">eval()</tt></a> also has the effect of interpreting numbers as Python expressions,
so that e.g. <tt class="docutils literal">eval('09')</tt> gives a syntax error because Python regards numbers
starting with &#8216;0&#8217; as octal (base 8).
</div>
<div class="section" id="how-do-i-convert-a-number-to-a-string">
<h3><a class="toc-backref" href="#id28">How do I convert a number to a string?</a><a class="headerlink" href="#how-do-i-convert-a-number-to-a-string" title="Permalink to this headline">¶</a></h3>
To convert, e.g., the number 144 to the string &#8216;144&#8217;, use the built-in type
constructor <a class="reference internal" href="../library/functions.html#str" title="str"><tt class="xref py py-func docutils literal">str()</tt></a>. If you want a hexadecimal or octal representation, use
the built-in functions <a class="reference internal" href="../library/functions.html#hex" title="hex"><tt class="xref py py-func docutils literal">hex()</tt></a> or <a class="reference internal" href="../library/functions.html#oct" title="oct"><tt class="xref py py-func docutils literal">oct()</tt></a>. For fancy formatting, see
the <a class="reference internal" href="../library/string.html#formatstrings">Format String Syntax</a> section, e.g. <tt class="docutils literal">&quot;{:04d}&quot;.format(144)</tt> yields
<tt class="docutils literal">'0144'</tt> and <tt class="docutils literal">&quot;{:.3f}&quot;.format(1/3)</tt> yields <tt class="docutils literal">'0.333'</tt>. You may also use
<a class="reference internal" href="../library/stdtypes.html#string-formatting">the % operator</a> on strings. See the library reference
manual for details.
</div>
<div class="section" id="how-do-i-modify-a-string-in-place">
<h3><a class="toc-backref" href="#id29">How do I modify a string in place?</a><a class="headerlink" href="#how-do-i-modify-a-string-in-place" title="Permalink to this headline">¶</a></h3>
You can&#8217;t, because strings are immutable. If you need an object with this
ability, try converting the string to a list or use the array module:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; s = &quot;Hello, world&quot;
&gt;&gt;&gt; a = list(s)
&gt;&gt;&gt; print a
[&#39;H&#39;, &#39;e&#39;, &#39;l&#39;, &#39;l&#39;, &#39;o&#39;, &#39;,&#39;, &#39; &#39;, &#39;w&#39;, &#39;o&#39;, &#39;r&#39;, &#39;l&#39;, &#39;d&#39;]
&gt;&gt;&gt; a[7:] = list(&quot;there!&quot;)
&gt;&gt;&gt; &#39;&#39;.join(a)
&#39;Hello, there!&#39;

&gt;&gt;&gt; import array
&gt;&gt;&gt; a = array.array(&#39;c&#39;, s)
&gt;&gt;&gt; print a
array(&#39;c&#39;, &#39;Hello, world&#39;)
&gt;&gt;&gt; a[0] = &#39;y&#39; ; print a
array(&#39;c&#39;, &#39;yello world&#39;)
&gt;&gt;&gt; a.tostring()
&#39;yello, world&#39;
</pre></div>
</div>
</div>
<div class="section" id="how-do-i-use-strings-to-call-functions-methods">
<h3><a class="toc-backref" href="#id30">How do I use strings to call functions/methods?</a><a class="headerlink" href="#how-do-i-use-strings-to-call-functions-methods" title="Permalink to this headline">¶</a></h3>
There are various techniques.
<ul>
<li>The best is to use a dictionary that maps strings to functions. The primary
advantage of this technique is that the strings do not need to match the names
of the functions. This is also the primary technique used to emulate a case
construct:
<div class="highlight-python"><div class="highlight"><pre>def a():
 pass

def b():
 pass

dispatch = {&#39;go&#39;: a, &#39;stop&#39;: b} # Note lack of parens for funcs

dispatch[get_input()]() # Note trailing parens to call function
</pre></div>
</div>
</li>
<li>Use the built-in function <a class="reference internal" href="../library/functions.html#getattr" title="getattr"><tt class="xref py py-func docutils literal">getattr()</tt></a>:
<div class="highlight-python"><div class="highlight"><pre>import foo
getattr(foo, &#39;bar&#39;)()
</pre></div>
</div>
Note that <a class="reference internal" href="../library/functions.html#getattr" title="getattr"><tt class="xref py py-func docutils literal">getattr()</tt></a> works on any object, including classes, class
instances, modules, and so on.
This is used in several places in the standard library, like this:
<div class="highlight-python"><div class="highlight"><pre>class Foo:
 def do_foo(self):
 ...

def do_bar(self):
 ...

f = getattr(foo_instance, &#39;do_&#39; + opname)
f()
</pre></div>
</div>
</li>
<li>Use <a class="reference internal" href="../library/functions.html#locals" title="locals"><tt class="xref py py-func docutils literal">locals()</tt></a> or <a class="reference internal" href="../library/functions.html#eval" title="eval"><tt class="xref py py-func docutils literal">eval()</tt></a> to resolve the function name:
<div class="highlight-python"><div class="highlight"><pre>def myFunc():
 print &quot;hello&quot;

fname = &quot;myFunc&quot;

f = locals()[fname]
f()

f = eval(fname)
f()
</pre></div>
</div>
Note: Using <a class="reference internal" href="../library/functions.html#eval" title="eval"><tt class="xref py py-func docutils literal">eval()</tt></a> is slow and dangerous. If you don&#8217;t have absolute
control over the contents of the string, someone could pass a string that
resulted in an arbitrary function being executed.
</li>
</ul>
</div>
<div class="section" id="is-there-an-equivalent-to-perl-s-chomp-for-removing-trailing-newlines-from-strings">
<h3><a class="toc-backref" href="#id31">Is there an equivalent to Perl&#8217;s chomp() for removing trailing newlines from strings?</a><a class="headerlink" href="#is-there-an-equivalent-to-perl-s-chomp-for-removing-trailing-newlines-from-strings" title="Permalink to this headline">¶</a></h3>
Starting with Python 2.2, you can use <tt class="docutils literal">S.rstrip(&quot;\r\n&quot;)</tt> to remove all
occurrences of any line terminator from the end of the string <tt class="docutils literal">S</tt> without
removing other trailing whitespace. If the string <tt class="docutils literal">S</tt> represents more than
one line, with several empty lines at the end, the line terminators for all the
blank lines will be removed:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; lines = (&quot;line 1 \r\n&quot;
... &quot;\r\n&quot;
... &quot;\r\n&quot;)
&gt;&gt;&gt; lines.rstrip(&quot;\n\r&quot;)
&#39;line 1 &#39;
</pre></div>
</div>
Since this is typically only desired when reading text one line at a time, using
<tt class="docutils literal">S.rstrip()</tt> this way works well.
For older versions of Python, there are two partial substitutes:
<ul class="simple">
<li>If you want to remove all trailing whitespace, use the <tt class="docutils literal">rstrip()</tt> method of
string objects. This removes all trailing whitespace, not just a single
newline.</li>
<li>Otherwise, if there is only one line in the string <tt class="docutils literal">S</tt>, use
<tt class="docutils literal">S.splitlines()[0]</tt>.</li>
</ul>
</div>
<div class="section" id="is-there-a-scanf-or-sscanf-equivalent">
<h3><a class="toc-backref" href="#id32">Is there a scanf() or sscanf() equivalent?</a><a class="headerlink" href="#is-there-a-scanf-or-sscanf-equivalent" title="Permalink to this headline">¶</a></h3>
Not as such.
For simple input parsing, the easiest approach is usually to split the line into
whitespace-delimited words using the <a class="reference internal" href="../library/stdtypes.html#str.split" title="str.split"><tt class="xref py py-meth docutils literal">split()</tt></a> method of string objects
and then convert decimal strings to numeric values using <a class="reference internal" href="../library/functions.html#int" title="int"><tt class="xref py py-func docutils literal">int()</tt></a> or
<a class="reference internal" href="../library/functions.html#float" title="float"><tt class="xref py py-func docutils literal">float()</tt></a>. <tt class="docutils literal">split()</tt> supports an optional &#8220;sep&#8221; parameter which is useful
if the line uses something other than whitespace as a separator.
For more complicated input parsing, regular expressions are more powerful
than C&#8217;s <tt class="xref c c-func docutils literal">sscanf()</tt> and better suited for the task.
</div>
<div class="section" id="what-does-unicodeerror-ascii-decoding-encoding-error-ordinal-not-in-range-128-mean">
<h3><a class="toc-backref" href="#id33">What does &#8216;UnicodeError: ASCII [decoding,encoding] error: ordinal not in range(128)&#8217; mean?</a><a class="headerlink" href="#what-does-unicodeerror-ascii-decoding-encoding-error-ordinal-not-in-range-128-mean" title="Permalink to this headline">¶</a></h3>
This error indicates that your Python installation can handle only 7-bit ASCII
strings. There are a couple ways to fix or work around the problem.
If your programs must handle data in arbitrary character set encodings, the
environment the application runs in will generally identify the encoding of the
data it is handing you. You need to convert the input to Unicode data using
that encoding. For example, a program that handles email or web input will
typically find character set encoding information in Content-Type headers. This
can then be used to properly convert input data to Unicode. Assuming the string
referred to by <tt class="docutils literal">value</tt> is encoded as UTF-8:
<div class="highlight-python"><div class="highlight"><pre>value = unicode(value, &quot;utf-8&quot;)
</pre></div>
</div>
will return a Unicode object. If the data is not correctly encoded as UTF-8,
the above call will raise a <a class="reference internal" href="../library/exceptions.html#exceptions.UnicodeError" title="exceptions.UnicodeError"><tt class="xref py py-exc docutils literal">UnicodeError</tt></a> exception.
If you only want strings converted to Unicode which have non-ASCII data, you can
try converting them first assuming an ASCII encoding, and then generate Unicode
objects if that fails:
<div class="highlight-python"><div class="highlight"><pre>try:
 x = unicode(value, &quot;ascii&quot;)
except UnicodeError:
 value = unicode(value, &quot;utf-8&quot;)
else:
 # value was valid ASCII data
 pass
</pre></div>
</div>
It&#8217;s possible to set a default encoding in a file called <tt class="docutils literal">sitecustomize.py</tt>
that&#8217;s part of the Python library. However, this isn&#8217;t recommended because
changing the Python-wide default encoding may cause third-party extension
modules to fail.
Note that on Windows, there is an encoding known as &#8220;mbcs&#8221;, which uses an
encoding specific to your current locale. In many cases, and particularly when
working with COM, this may be an appropriate default encoding to use.
</div>
</div>
<div class="section" id="sequences-tuples-lists">
<h2><a class="toc-backref" href="#id34">Sequences (Tuples/Lists)</a><a class="headerlink" href="#sequences-tuples-lists" title="Permalink to this headline">¶</a></h2>
<div class="section" id="how-do-i-convert-between-tuples-and-lists">
<h3><a class="toc-backref" href="#id35">How do I convert between tuples and lists?</a><a class="headerlink" href="#how-do-i-convert-between-tuples-and-lists" title="Permalink to this headline">¶</a></h3>
The type constructor <tt class="docutils literal">tuple(seq)</tt> converts any sequence (actually, any
iterable) into a tuple with the same items in the same order.
For example, <tt class="docutils literal">tuple([1, 2, 3])</tt> yields <tt class="docutils literal">(1, 2, 3)</tt> and <tt class="docutils literal">tuple('abc')</tt>
yields <tt class="docutils literal">('a', 'b', 'c')</tt>. If the argument is a tuple, it does not make a copy
but returns the same object, so it is cheap to call <a class="reference internal" href="../library/functions.html#tuple" title="tuple"><tt class="xref py py-func docutils literal">tuple()</tt></a> when you
aren&#8217;t sure that an object is already a tuple.
The type constructor <tt class="docutils literal">list(seq)</tt> converts any sequence or iterable into a list
with the same items in the same order. For example, <tt class="docutils literal">list((1, 2, 3))</tt> yields
<tt class="docutils literal">[1, 2, 3]</tt> and <tt class="docutils literal">list('abc')</tt> yields <tt class="docutils literal">['a', 'b', 'c']</tt>. If the argument
is a list, it makes a copy just like <tt class="docutils literal">seq[:]</tt> would.
</div>
<div class="section" id="what-s-a-negative-index">
<h3><a class="toc-backref" href="#id36">What&#8217;s a negative index?</a><a class="headerlink" href="#what-s-a-negative-index" title="Permalink to this headline">¶</a></h3>
Python sequences are indexed with positive numbers and negative numbers. For
positive numbers 0 is the first index 1 is the second index and so forth. For
negative indices -1 is the last index and -2 is the penultimate (next to last)
index and so forth. Think of <tt class="docutils literal">seq[-n]</tt> as the same as <tt class="docutils literal">seq[len(seq)-n]</tt>.
Using negative indices can be very convenient. For example <tt class="docutils literal">S[:-1]</tt> is all of
the string except for its last character, which is useful for removing the
trailing newline from a string.
</div>
<div class="section" id="how-do-i-iterate-over-a-sequence-in-reverse-order">
<h3><a class="toc-backref" href="#id37">How do I iterate over a sequence in reverse order?</a><a class="headerlink" href="#how-do-i-iterate-over-a-sequence-in-reverse-order" title="Permalink to this headline">¶</a></h3>
Use the <a class="reference internal" href="../library/functions.html#reversed" title="reversed"><tt class="xref py py-func docutils literal">reversed()</tt></a> built-in function, which is new in Python 2.4:
<div class="highlight-python"><div class="highlight"><pre>for x in reversed(sequence):
 ... # do something with x...
</pre></div>
</div>
This won&#8217;t touch your original sequence, but build a new copy with reversed
order to iterate over.
With Python 2.3, you can use an extended slice syntax:
<div class="highlight-python"><div class="highlight"><pre>for x in sequence[::-1]:
 ... # do something with x...
</pre></div>
</div>
</div>
<div class="section" id="how-do-you-remove-duplicates-from-a-list">
<h3><a class="toc-backref" href="#id38">How do you remove duplicates from a list?</a><a class="headerlink" href="#how-do-you-remove-duplicates-from-a-list" title="Permalink to this headline">¶</a></h3>
See the Python Cookbook for a long discussion of many ways to do this:
<blockquote>
<div><a class="reference external" href="http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/52560">http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/52560</a></div></blockquote>
If you don&#8217;t mind reordering the list, sort it and then scan from the end of the
list, deleting duplicates as you go:
<div class="highlight-python"><div class="highlight"><pre>if mylist:
 mylist.sort()
 last = mylist[-1]
 for i in range(len(mylist)-2, -1, -1):
 if last == mylist[i]:
 del mylist[i]
 else:
 last = mylist[i]
</pre></div>
</div>
If all elements of the list may be used as dictionary keys (i.e. they are all
hashable) this is often faster
<div class="highlight-python"><div class="highlight"><pre>d = {}
for x in mylist:
 d[x] = 1
mylist = list(d.keys())
</pre></div>
</div>
In Python 2.5 and later, the following is possible instead:
<div class="highlight-python"><div class="highlight"><pre>mylist = list(set(mylist))
</pre></div>
</div>
This converts the list into a set, thereby removing duplicates, and then back
into a list.
</div>
<div class="section" id="how-do-you-make-an-array-in-python">
<h3><a class="toc-backref" href="#id39">How do you make an array in Python?</a><a class="headerlink" href="#how-do-you-make-an-array-in-python" title="Permalink to this headline">¶</a></h3>
Use a list:
<div class="highlight-python"><div class="highlight"><pre>[&quot;this&quot;, 1, &quot;is&quot;, &quot;an&quot;, &quot;array&quot;]
</pre></div>
</div>
Lists are equivalent to C or Pascal arrays in their time complexity; the primary
difference is that a Python list can contain objects of many different types.
The <tt class="docutils literal">array</tt> module also provides methods for creating arrays of fixed types
with compact representations, but they are slower to index than lists. Also
note that the Numeric extensions and others define array-like structures with
various characteristics as well.
To get Lisp-style linked lists, you can emulate cons cells using tuples:
<div class="highlight-python"><div class="highlight"><pre>lisp_list = (&quot;like&quot;, (&quot;this&quot;, (&quot;example&quot;, None) ) )
</pre></div>
</div>
If mutability is desired, you could use lists instead of tuples. Here the
analogue of lisp car is <tt class="docutils literal">lisp_list[0]</tt> and the analogue of cdr is
<tt class="docutils literal">lisp_list[1]</tt>. Only do this if you&#8217;re sure you really need to, because it&#8217;s
usually a lot slower than using Python lists.
</div>
<div class="section" id="how-do-i-create-a-multidimensional-list">
<h3><a class="toc-backref" href="#id40">How do I create a multidimensional list?</a><a class="headerlink" href="#how-do-i-create-a-multidimensional-list" title="Permalink to this headline">¶</a></h3>
You probably tried to make a multidimensional array like this:
<div class="highlight-python"><div class="highlight"><pre>A = [[None] * 2] * 3
</pre></div>
</div>
This looks correct if you print it:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; A
[[None, None], [None, None], [None, None]]
</pre></div>
</div>
But when you assign a value, it shows up in multiple places:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; A[0][0] = 5
&gt;&gt;&gt; A
[[5, None], [5, None], [5, None]]
</pre></div>
</div>
The reason is that replicating a list with <tt class="docutils literal">*</tt> doesn&#8217;t create copies, it only
creates references to the existing objects. The <tt class="docutils literal">*3</tt> creates a list
containing 3 references to the same list of length two. Changes to one row will
show in all rows, which is almost certainly not what you want.
The suggested approach is to create a list of the desired length first and then
fill in each element with a newly created list:
<div class="highlight-python"><div class="highlight"><pre>A = [None] * 3
for i in range(3):
 A[i] = [None] * 2
</pre></div>
</div>
This generates a list containing 3 different lists of length two. You can also
use a list comprehension:
<div class="highlight-python"><div class="highlight"><pre>w, h = 2, 3
A = [[None] * w for i in range(h)]
</pre></div>
</div>
Or, you can use an extension that provides a matrix datatype; <a class="reference external" href="http://numpy.scipy.org/">Numeric Python</a> is the best known.
</div>
<div class="section" id="how-do-i-apply-a-method-to-a-sequence-of-objects">
<h3><a class="toc-backref" href="#id41">How do I apply a method to a sequence of objects?</a><a class="headerlink" href="#how-do-i-apply-a-method-to-a-sequence-of-objects" title="Permalink to this headline">¶</a></h3>
Use a list comprehension:
<div class="highlight-python"><div class="highlight"><pre>result = [obj.method() for obj in mylist]
</pre></div>
</div>
More generically, you can try the following function:
<div class="highlight-python"><div class="highlight"><pre>def method_map(objects, method, arguments):
 &quot;&quot;&quot;method_map([a,b], &quot;meth&quot;, (1,2)) gives [a.meth(1,2), b.meth(1,2)]&quot;&quot;&quot;
 nobjects = len(objects)
 methods = map(getattr, objects, [method]*nobjects)
 return map(apply, methods, [arguments]*nobjects)
</pre></div>
</div>
</div>
</div>
<div class="section" id="dictionaries">
<h2><a class="toc-backref" href="#id42">Dictionaries</a><a class="headerlink" href="#dictionaries" title="Permalink to this headline">¶</a></h2>
<div class="section" id="how-can-i-get-a-dictionary-to-display-its-keys-in-a-consistent-order">
<h3><a class="toc-backref" href="#id43">How can I get a dictionary to display its keys in a consistent order?</a><a class="headerlink" href="#how-can-i-get-a-dictionary-to-display-its-keys-in-a-consistent-order" title="Permalink to this headline">¶</a></h3>
You can&#8217;t. Dictionaries store their keys in an unpredictable order, so the
display order of a dictionary&#8217;s elements will be similarly unpredictable.
This can be frustrating if you want to save a printable version to a file, make
some changes and then compare it with some other printed dictionary. In this
case, use the <tt class="docutils literal">pprint</tt> module to pretty-print the dictionary; the items will
be presented in order sorted by the key.
A more complicated solution is to subclass <tt class="docutils literal">dict</tt> to create a
<tt class="docutils literal">SortedDict</tt> class that prints itself in a predictable order. Here&#8217;s one
simpleminded implementation of such a class:
<div class="highlight-python"><div class="highlight"><pre>class SortedDict(dict):
 def __repr__(self):
 keys = sorted(self.keys())
 result = (&quot;{!r}: {!r}&quot;.format(k, self[k]) for k in keys)
 return &quot;{{{}}}&quot;.format(&quot;, &quot;.join(result))

__str__ = __repr__
</pre></div>
</div>
This will work for many common situations you might encounter, though it&#8217;s far
from a perfect solution. The largest flaw is that if some values in the
dictionary are also dictionaries, their values won&#8217;t be presented in any
particular order.
</div>
<div class="section" id="i-want-to-do-a-complicated-sort-can-you-do-a-schwartzian-transform-in-python">
<h3><a class="toc-backref" href="#id44">I want to do a complicated sort: can you do a Schwartzian Transform in Python?</a><a class="headerlink" href="#i-want-to-do-a-complicated-sort-can-you-do-a-schwartzian-transform-in-python" title="Permalink to this headline">¶</a></h3>
The technique, attributed to Randal Schwartz of the Perl community, sorts the
elements of a list by a metric which maps each element to its &#8220;sort value&#8221;. In
Python, just use the <tt class="docutils literal">key</tt> argument for the <tt class="docutils literal">sort()</tt> method:
<div class="highlight-python"><div class="highlight"><pre>Isorted = L[:]
Isorted.sort(key=lambda s: int(s[10:15]))
</pre></div>
</div>
The <tt class="docutils literal">key</tt> argument is new in Python 2.4, for older versions this kind of
sorting is quite simple to do with list comprehensions. To sort a list of
strings by their uppercase values:
<div class="highlight-python"><div class="highlight"><pre>tmp1 = [(x.upper(), x) for x in L] # Schwartzian transform
tmp1.sort()
Usorted = [x[1] for x in tmp1]
</pre></div>
</div>
To sort by the integer value of a subfield extending from positions 10-15 in
each string:
<div class="highlight-python"><div class="highlight"><pre>tmp2 = [(int(s[10:15]), s) for s in L] # Schwartzian transform
tmp2.sort()
Isorted = [x[1] for x in tmp2]
</pre></div>
</div>
Note that Isorted may also be computed by
<div class="highlight-python"><div class="highlight"><pre>def intfield(s):
 return int(s[10:15])

def Icmp(s1, s2):
 return cmp(intfield(s1), intfield(s2))

Isorted = L[:]
Isorted.sort(Icmp)
</pre></div>
</div>
but since this method calls <tt class="docutils literal">intfield()</tt> many times for each element of L, it
is slower than the Schwartzian Transform.
</div>
<div class="section" id="how-can-i-sort-one-list-by-values-from-another-list">
<h3><a class="toc-backref" href="#id45">How can I sort one list by values from another list?</a><a class="headerlink" href="#how-can-i-sort-one-list-by-values-from-another-list" title="Permalink to this headline">¶</a></h3>
Merge them into a single list of tuples, sort the resulting list, and then pick
out the element you want.
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; list1 = [&quot;what&quot;, &quot;I&#39;m&quot;, &quot;sorting&quot;, &quot;by&quot;]
&gt;&gt;&gt; list2 = [&quot;something&quot;, &quot;else&quot;, &quot;to&quot;, &quot;sort&quot;]
&gt;&gt;&gt; pairs = zip(list1, list2)
&gt;&gt;&gt; pairs
[(&#39;what&#39;, &#39;something&#39;), (&quot;I&#39;m&quot;, &#39;else&#39;), (&#39;sorting&#39;, &#39;to&#39;), (&#39;by&#39;, &#39;sort&#39;)]
&gt;&gt;&gt; pairs.sort()
&gt;&gt;&gt; result = [ x[1] for x in pairs ]
&gt;&gt;&gt; result
[&#39;else&#39;, &#39;sort&#39;, &#39;to&#39;, &#39;something&#39;]
</pre></div>
</div>
An alternative for the last step is:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; result = []
&gt;&gt;&gt; for p in pairs: result.append(p[1])
</pre></div>
</div>
If you find this more legible, you might prefer to use this instead of the final
list comprehension. However, it is almost twice as slow for long lists. Why?
First, the <tt class="docutils literal">append()</tt> operation has to reallocate memory, and while it uses
some tricks to avoid doing that each time, it still has to do it occasionally,
and that costs quite a bit. Second, the expression &#8220;result.append&#8221; requires an
extra attribute lookup, and third, there&#8217;s a speed reduction from having to make
all those function calls.
</div>
</div>
<div class="section" id="objects">
<h2><a class="toc-backref" href="#id46">Objects</a><a class="headerlink" href="#objects" title="Permalink to this headline">¶</a></h2>
<div class="section" id="what-is-a-class">
<h3><a class="toc-backref" href="#id47">What is a class?</a><a class="headerlink" href="#what-is-a-class" title="Permalink to this headline">¶</a></h3>
A class is the particular object type created by executing a class statement.
Class objects are used as templates to create instance objects, which embody
both the data (attributes) and code (methods) specific to a datatype.
A class can be based on one or more other classes, called its base class(es). It
then inherits the attributes and methods of its base classes. This allows an
object model to be successively refined by inheritance. You might have a
generic <tt class="docutils literal">Mailbox</tt> class that provides basic accessor methods for a mailbox,
and subclasses such as <tt class="docutils literal">MboxMailbox</tt>, <tt class="docutils literal">MaildirMailbox</tt>, <tt class="docutils literal">OutlookMailbox</tt>
that handle various specific mailbox formats.
</div>
<div class="section" id="what-is-a-method">
<h3><a class="toc-backref" href="#id48">What is a method?</a><a class="headerlink" href="#what-is-a-method" title="Permalink to this headline">¶</a></h3>
A method is a function on some object <tt class="docutils literal">x</tt> that you normally call as
<tt class="docutils literal">x.name(arguments...)</tt>. Methods are defined as functions inside the class
definition:
<div class="highlight-python"><div class="highlight"><pre>class C:
 def meth (self, arg):
 return arg * 2 + self.attribute
</pre></div>
</div>
</div>
<div class="section" id="what-is-self">
<h3><a class="toc-backref" href="#id49">What is self?</a><a class="headerlink" href="#what-is-self" title="Permalink to this headline">¶</a></h3>
Self is merely a conventional name for the first argument of a method. A method
defined as <tt class="docutils literal">meth(self, a, b, c)</tt> should be called as <tt class="docutils literal">x.meth(a, b, c)</tt> for
some instance <tt class="docutils literal">x</tt> of the class in which the definition occurs; the called
method will think it is called as <tt class="docutils literal">meth(x, a, b, c)</tt>.
See also <a class="reference internal" href="design.html#why-self">Why must &#8216;self&#8217; be used explicitly in method definitions and calls?</a>.
</div>
<div class="section" id="how-do-i-check-if-an-object-is-an-instance-of-a-given-class-or-of-a-subclass-of-it">
<h3><a class="toc-backref" href="#id50">How do I check if an object is an instance of a given class or of a subclass of it?</a><a class="headerlink" href="#how-do-i-check-if-an-object-is-an-instance-of-a-given-class-or-of-a-subclass-of-it" title="Permalink to this headline">¶</a></h3>
Use the built-in function <tt class="docutils literal">isinstance(obj, cls)</tt>. You can check if an object
is an instance of any of a number of classes by providing a tuple instead of a
single class, e.g. <tt class="docutils literal">isinstance(obj, (class1, class2, ...))</tt>, and can also
check whether an object is one of Python&#8217;s built-in types, e.g.
<tt class="docutils literal">isinstance(obj, str)</tt> or <tt class="docutils literal">isinstance(obj, (int, long, float, complex))</tt>.
Note that most programs do not use <a class="reference internal" href="../library/functions.html#isinstance" title="isinstance"><tt class="xref py py-func docutils literal">isinstance()</tt></a> on user-defined classes
very often. If you are developing the classes yourself, a more proper
object-oriented style is to define methods on the classes that encapsulate a
particular behaviour, instead of checking the object&#8217;s class and doing a
different thing based on what class it is. For example, if you have a function
that does something:
<div class="highlight-python"><pre>def search(obj):
 if isinstance(obj, Mailbox):
 # ... code to search a mailbox
 elif isinstance(obj, Document):
 # ... code to search a document
 elif ...</pre>
</div>
A better approach is to define a <tt class="docutils literal">search()</tt> method on all the classes and just
call it:
<div class="highlight-python"><pre>class Mailbox:
 def search(self):
 # ... code to search a mailbox

class Document:
    def search(self):
        # ... code to search a document

obj.search()</pre>
</div>
</div>
<div class="section" id="what-is-delegation">
<h3><a class="toc-backref" href="#id51">What is delegation?</a><a class="headerlink" href="#what-is-delegation" title="Permalink to this headline">¶</a></h3>
Delegation is an object oriented technique (also called a design pattern).
Let&#8217;s say you have an object <tt class="docutils literal">x</tt> and want to change the behaviour of just one
of its methods. You can create a new class that provides a new implementation
of the method you&#8217;re interested in changing and delegates all other methods to
the corresponding method of <tt class="docutils literal">x</tt>.
Python programmers can easily implement delegation. For example, the following
class implements a class that behaves like a file but converts all written data
to uppercase:
<div class="highlight-python"><div class="highlight"><pre>class UpperOut:

def __init__(self, outfile):
 self._outfile = outfile

def write(self, s):
 self._outfile.write(s.upper())

def __getattr__(self, name):
 return getattr(self._outfile, name)
</pre></div>
</div>
Here the <tt class="docutils literal">UpperOut</tt> class redefines the <tt class="docutils literal">write()</tt> method to convert the
argument string to uppercase before calling the underlying
<tt class="docutils literal">self.__outfile.write()</tt> method. All other methods are delegated to the
underlying <tt class="docutils literal">self.__outfile</tt> object. The delegation is accomplished via the
<tt class="docutils literal">__getattr__</tt> method; consult <a class="reference internal" href="../reference/datamodel.html#attribute-access">the language reference</a>
for more information about controlling attribute access.
Note that for more general cases delegation can get trickier. When attributes
must be set as well as retrieved, the class must define a <a class="reference internal" href="../reference/datamodel.html#object.__setattr__" title="object.__setattr__"><tt class="xref py py-meth docutils literal">__setattr__()</tt></a>
method too, and it must do so carefully. The basic implementation of
<a class="reference internal" href="../reference/datamodel.html#object.__setattr__" title="object.__setattr__"><tt class="xref py py-meth docutils literal">__setattr__()</tt></a> is roughly equivalent to the following:
<div class="highlight-python"><div class="highlight"><pre>class X:
 ...
 def __setattr__(self, name, value):
 self.__dict__[name] = value
 ...
</pre></div>
</div>
Most <a class="reference internal" href="../reference/datamodel.html#object.__setattr__" title="object.__setattr__"><tt class="xref py py-meth docutils literal">__setattr__()</tt></a> implementations must modify <tt class="docutils literal">self.__dict__</tt> to store
local state for self without causing an infinite recursion.
</div>
<div class="section" id="how-do-i-call-a-method-defined-in-a-base-class-from-a-derived-class-that-overrides-it">
<h3><a class="toc-backref" href="#id52">How do I call a method defined in a base class from a derived class that overrides it?</a><a class="headerlink" href="#how-do-i-call-a-method-defined-in-a-base-class-from-a-derived-class-that-overrides-it" title="Permalink to this headline">¶</a></h3>
If you&#8217;re using new-style classes, use the built-in <a class="reference internal" href="../library/functions.html#super" title="super"><tt class="xref py py-func docutils literal">super()</tt></a> function:
<div class="highlight-python"><div class="highlight"><pre>class Derived(Base):
 def meth (self):
 super(Derived, self).meth()
</pre></div>
</div>
If you&#8217;re using classic classes: For a class definition such as <tt class="docutils literal">class
Derived(Base): ...</tt> you can call method <tt class="docutils literal">meth()</tt> defined in <tt class="docutils literal">Base</tt> (or one
of <tt class="docutils literal">Base</tt>&#8216;s base classes) as <tt class="docutils literal">Base.meth(self, arguments...)</tt>. Here,
<tt class="docutils literal">Base.meth</tt> is an unbound method, so you need to provide the <tt class="docutils literal">self</tt>
argument.
</div>
<div class="section" id="how-can-i-organize-my-code-to-make-it-easier-to-change-the-base-class">
<h3><a class="toc-backref" href="#id53">How can I organize my code to make it easier to change the base class?</a><a class="headerlink" href="#how-can-i-organize-my-code-to-make-it-easier-to-change-the-base-class" title="Permalink to this headline">¶</a></h3>
You could define an alias for the base class, assign the real base class to it
before your class definition, and use the alias throughout your class. Then all
you have to change is the value assigned to the alias. Incidentally, this trick
is also handy if you want to decide dynamically (e.g. depending on availability
of resources) which base class to use. Example:
<div class="highlight-python"><pre>BaseAlias = &lt;real base class&gt;

class Derived(BaseAlias):
 def meth(self):
 BaseAlias.meth(self)
 ...</pre>
</div>
</div>
<div class="section" id="how-do-i-create-static-class-data-and-static-class-methods">
<h3><a class="toc-backref" href="#id54">How do I create static class data and static class methods?</a><a class="headerlink" href="#how-do-i-create-static-class-data-and-static-class-methods" title="Permalink to this headline">¶</a></h3>
Both static data and static methods (in the sense of C++ or Java) are supported
in Python.
For static data, simply define a class attribute. To assign a new value to the
attribute, you have to explicitly use the class name in the assignment:
<div class="highlight-python"><div class="highlight"><pre>class C:
 count = 0 # number of times C.__init__ called

def __init__(self):
 C.count = C.count + 1

def getcount(self):
 return C.count # or return self.count
</pre></div>
</div>
<tt class="docutils literal">c.count</tt> also refers to <tt class="docutils literal">C.count</tt> for any <tt class="docutils literal">c</tt> such that <tt class="docutils literal">isinstance(c,
C)</tt> holds, unless overridden by <tt class="docutils literal">c</tt> itself or by some class on the base-class
search path from <tt class="docutils literal">c.__class__</tt> back to <tt class="docutils literal">C</tt>.
Caution: within a method of C, an assignment like <tt class="docutils literal">self.count = 42</tt> creates a
new and unrelated instance named &#8220;count&#8221; in <tt class="docutils literal">self</tt>&#8216;s own dict. Rebinding of a
class-static data name must always specify the class whether inside a method or
not:
<div class="highlight-python"><div class="highlight"><pre>C.count = 314
</pre></div>
</div>
Static methods are possible since Python 2.2:
<div class="highlight-python"><div class="highlight"><pre>class C:
 def static(arg1, arg2, arg3):
 # No &#39;self&#39; parameter!
 ...
 static = staticmethod(static)
</pre></div>
</div>
With Python 2.4&#8217;s decorators, this can also be written as
<div class="highlight-python"><div class="highlight"><pre>class C:
 @staticmethod
 def static(arg1, arg2, arg3):
 # No &#39;self&#39; parameter!
 ...
</pre></div>
</div>
However, a far more straightforward way to get the effect of a static method is
via a simple module-level function:
<div class="highlight-python"><div class="highlight"><pre>def getcount():
 return C.count
</pre></div>
</div>
If your code is structured so as to define one class (or tightly related class
hierarchy) per module, this supplies the desired encapsulation.
</div>
<div class="section" id="how-can-i-overload-constructors-or-methods-in-python">
<h3><a class="toc-backref" href="#id55">How can I overload constructors (or methods) in Python?</a><a class="headerlink" href="#how-can-i-overload-constructors-or-methods-in-python" title="Permalink to this headline">¶</a></h3>
This answer actually applies to all methods, but the question usually comes up
first in the context of constructors.
In C++ you&#8217;d write
<div class="highlight-c"><div class="highlight"><pre>class C {
 C() { cout &lt;&lt; &quot;No arguments\n&quot;; }
 C(int i) { cout &lt;&lt; &quot;Argument is &quot; &lt;&lt; i &lt;&lt; &quot;\n&quot;; }
}
</pre></div>
</div>
In Python you have to write a single constructor that catches all cases using
default arguments. For example:
<div class="highlight-python"><div class="highlight"><pre>class C:
 def __init__(self, i=None):
 if i is None:
 print &quot;No arguments&quot;
 else:
 print &quot;Argument is&quot;, i
</pre></div>
</div>
This is not entirely equivalent, but close enough in practice.
You could also try a variable-length argument list, e.g.
<div class="highlight-python"><div class="highlight"><pre>def __init__(self, *args):
 ...
</pre></div>
</div>
The same approach works for all method definitions.
</div>
<div class="section" id="i-try-to-use-spam-and-i-get-an-error-about-someclassname-spam">
<h3><a class="toc-backref" href="#id56">I try to use __spam and I get an error about _SomeClassName__spam.</a><a class="headerlink" href="#i-try-to-use-spam-and-i-get-an-error-about-someclassname-spam" title="Permalink to this headline">¶</a></h3>
Variable names with double leading underscores are &#8220;mangled&#8221; to provide a simple
but effective way to define class private variables. Any identifier of the form
<tt class="docutils literal">__spam</tt> (at least two leading underscores, at most one trailing underscore)
is textually replaced with <tt class="docutils literal">_classname__spam</tt>, where <tt class="docutils literal">classname</tt> is the
current class name with any leading underscores stripped.
This doesn&#8217;t guarantee privacy: an outside user can still deliberately access
the &#8220;_classname__spam&#8221; attribute, and private values are visible in the object&#8217;s
<tt class="docutils literal">__dict__</tt>. Many Python programmers never bother to use private variable
names at all.
</div>
<div class="section" id="my-class-defines-del-but-it-is-not-called-when-i-delete-the-object">
<h3><a class="toc-backref" href="#id57">My class defines __del__ but it is not called when I delete the object.</a><a class="headerlink" href="#my-class-defines-del-but-it-is-not-called-when-i-delete-the-object" title="Permalink to this headline">¶</a></h3>
There are several possible reasons for this.
The del statement does not necessarily call <a class="reference internal" href="../reference/datamodel.html#object.__del__" title="object.__del__"><tt class="xref py py-meth docutils literal">__del__()</tt></a> &#8211; it simply
decrements the object&#8217;s reference count, and if this reaches zero
<a class="reference internal" href="../reference/datamodel.html#object.__del__" title="object.__del__"><tt class="xref py py-meth docutils literal">__del__()</tt></a> is called.
If your data structures contain circular links (e.g. a tree where each child has
a parent reference and each parent has a list of children) the reference counts
will never go back to zero. Once in a while Python runs an algorithm to detect
such cycles, but the garbage collector might run some time after the last
reference to your data structure vanishes, so your <a class="reference internal" href="../reference/datamodel.html#object.__del__" title="object.__del__"><tt class="xref py py-meth docutils literal">__del__()</tt></a> method may be
called at an inconvenient and random time. This is inconvenient if you&#8217;re trying
to reproduce a problem. Worse, the order in which object&#8217;s <a class="reference internal" href="../reference/datamodel.html#object.__del__" title="object.__del__"><tt class="xref py py-meth docutils literal">__del__()</tt></a>
methods are executed is arbitrary. You can run <a class="reference internal" href="../library/gc.html#gc.collect" title="gc.collect"><tt class="xref py py-func docutils literal">gc.collect()</tt></a> to force a
collection, but there are pathological cases where objects will never be
collected.
Despite the cycle collector, it&#8217;s still a good idea to define an explicit
<tt class="docutils literal">close()</tt> method on objects to be called whenever you&#8217;re done with them. The
<tt class="docutils literal">close()</tt> method can then remove attributes that refer to subobjecs. Don&#8217;t
call <a class="reference internal" href="../reference/datamodel.html#object.__del__" title="object.__del__"><tt class="xref py py-meth docutils literal">__del__()</tt></a> directly &#8211; <a class="reference internal" href="../reference/datamodel.html#object.__del__" title="object.__del__"><tt class="xref py py-meth docutils literal">__del__()</tt></a> should call <tt class="docutils literal">close()</tt> and
<tt class="docutils literal">close()</tt> should make sure that it can be called more than once for the same
object.
Another way to avoid cyclical references is to use the <a class="reference internal" href="../library/weakref.html#module-weakref" title="weakref: Support for weak references and weak dictionaries."><tt class="xref py py-mod docutils literal">weakref</tt></a> module,
which allows you to point to objects without incrementing their reference count.
Tree data structures, for instance, should use weak references for their parent
and sibling references (if they need them!).
If the object has ever been a local variable in a function that caught an
expression in an except clause, chances are that a reference to the object still
exists in that function&#8217;s stack frame as contained in the stack trace.
Normally, calling <a class="reference internal" href="../library/sys.html#sys.exc_clear" title="sys.exc_clear"><tt class="xref py py-func docutils literal">sys.exc_clear()</tt></a> will take care of this by clearing the
last recorded exception.
Finally, if your <a class="reference internal" href="../reference/datamodel.html#object.__del__" title="object.__del__"><tt class="xref py py-meth docutils literal">__del__()</tt></a> method raises an exception, a warning message
is printed to <a class="reference internal" href="../library/sys.html#sys.stderr" title="sys.stderr"><tt class="xref py py-data docutils literal">sys.stderr</tt></a>.
</div>
<div class="section" id="how-do-i-get-a-list-of-all-instances-of-a-given-class">
<h3><a class="toc-backref" href="#id58">How do I get a list of all instances of a given class?</a><a class="headerlink" href="#how-do-i-get-a-list-of-all-instances-of-a-given-class" title="Permalink to this headline">¶</a></h3>
Python does not keep track of all instances of a class (or of a built-in type).
You can program the class&#8217;s constructor to keep track of all instances by
keeping a list of weak references to each instance.
</div>
</div>
<div class="section" id="modules">
<h2><a class="toc-backref" href="#id59">Modules</a><a class="headerlink" href="#modules" title="Permalink to this headline">¶</a></h2>
<div class="section" id="how-do-i-create-a-pyc-file">
<h3><a class="toc-backref" href="#id60">How do I create a .pyc file?</a><a class="headerlink" href="#how-do-i-create-a-pyc-file" title="Permalink to this headline">¶</a></h3>
When a module is imported for the first time (or when the source is more recent
than the current compiled file) a <tt class="docutils literal">.pyc</tt> file containing the compiled code
should be created in the same directory as the <tt class="docutils literal">.py</tt> file.
One reason that a <tt class="docutils literal">.pyc</tt> file may not be created is permissions problems with
the directory. This can happen, for example, if you develop as one user but run
as another, such as if you are testing with a web server. Creation of a .pyc
file is automatic if you&#8217;re importing a module and Python has the ability
(permissions, free space, etc...) to write the compiled module back to the
directory.
Running Python on a top level script is not considered an import and no <tt class="docutils literal">.pyc</tt>
will be created. For example, if you have a top-level module <tt class="docutils literal">abc.py</tt> that
imports another module <tt class="docutils literal">xyz.py</tt>, when you run abc, <tt class="docutils literal">xyz.pyc</tt> will be created
since xyz is imported, but no <tt class="docutils literal">abc.pyc</tt> file will be created since <tt class="docutils literal">abc.py</tt>
isn&#8217;t being imported.
If you need to create abc.pyc &#8211; that is, to create a .pyc file for a module
that is not imported &#8211; you can, using the <a class="reference internal" href="../library/py_compile.html#module-py_compile" title="py_compile: Generate byte-code files from Python source files."><tt class="xref py py-mod docutils literal">py_compile</tt></a> and
<a class="reference internal" href="../library/compileall.html#module-compileall" title="compileall: Tools for byte-compiling all Python source files in a directory tree."><tt class="xref py py-mod docutils literal">compileall</tt></a> modules.
The <a class="reference internal" href="../library/py_compile.html#module-py_compile" title="py_compile: Generate byte-code files from Python source files."><tt class="xref py py-mod docutils literal">py_compile</tt></a> module can manually compile any module. One way is to use
the <tt class="docutils literal">compile()</tt> function in that module interactively:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; import py_compile
&gt;&gt;&gt; py_compile.compile(&#39;abc.py&#39;)
</pre></div>
</div>
This will write the <tt class="docutils literal">.pyc</tt> to the same location as <tt class="docutils literal">abc.py</tt> (or you can
override that with the optional parameter <tt class="docutils literal">cfile</tt>).
You can also automatically compile all files in a directory or directories using
the <a class="reference internal" href="../library/compileall.html#module-compileall" title="compileall: Tools for byte-compiling all Python source files in a directory tree."><tt class="xref py py-mod docutils literal">compileall</tt></a> module. You can do it from the shell prompt by running
<tt class="docutils literal">compileall.py</tt> and providing the path of a directory containing Python files
to compile:
<div class="highlight-python"><pre>python -m compileall .</pre>
</div>
</div>
<div class="section" id="how-do-i-find-the-current-module-name">
<h3><a class="toc-backref" href="#id61">How do I find the current module name?</a><a class="headerlink" href="#how-do-i-find-the-current-module-name" title="Permalink to this headline">¶</a></h3>
A module can find out its own module name by looking at the predefined global
variable <tt class="docutils literal">__name__</tt>. If this has the value <tt class="docutils literal">'__main__'</tt>, the program is
running as a script. Many modules that are usually used by importing them also
provide a command-line interface or a self-test, and only execute this code
after checking <tt class="docutils literal">__name__</tt>:
<div class="highlight-python"><div class="highlight"><pre>def main():
 print &#39;Running test...&#39;
 ...

if __name__ == &#39;__main__&#39;:
 main()
</pre></div>
</div>
</div>
<div class="section" id="how-can-i-have-modules-that-mutually-import-each-other">
<h3><a class="toc-backref" href="#id62">How can I have modules that mutually import each other?</a><a class="headerlink" href="#how-can-i-have-modules-that-mutually-import-each-other" title="Permalink to this headline">¶</a></h3>
Suppose you have the following modules:
foo.py:
<div class="highlight-python"><div class="highlight"><pre>from bar import bar_var
foo_var = 1
</pre></div>
</div>
bar.py:
<div class="highlight-python"><div class="highlight"><pre>from foo import foo_var
bar_var = 2
</pre></div>
</div>
The problem is that the interpreter will perform the following steps:
<ul class="simple">
<li>main imports foo</li>
<li>Empty globals for foo are created</li>
<li>foo is compiled and starts executing</li>
<li>foo imports bar</li>
<li>Empty globals for bar are created</li>
<li>bar is compiled and starts executing</li>
<li>bar imports foo (which is a no-op since there already is a module named foo)</li>
<li>bar.foo_var = foo.foo_var</li>
</ul>
The last step fails, because Python isn&#8217;t done with interpreting <tt class="docutils literal">foo</tt> yet and
the global symbol dictionary for <tt class="docutils literal">foo</tt> is still empty.
The same thing happens when you use <tt class="docutils literal">import foo</tt>, and then try to access
<tt class="docutils literal">foo.foo_var</tt> in global code.
There are (at least) three possible workarounds for this problem.
Guido van Rossum recommends avoiding all uses of <tt class="docutils literal">from &lt;module&gt; import ...</tt>,
and placing all code inside functions. Initializations of global variables and
class variables should use constants or built-in functions only. This means
everything from an imported module is referenced as <tt class="docutils literal">&lt;module&gt;.&lt;name&gt;</tt>.
Jim Roskind suggests performing steps in the following order in each module:
<ul class="simple">
<li>exports (globals, functions, and classes that don&#8217;t need imported base
classes)</li>
<li><tt class="docutils literal">import</tt> statements</li>
<li>active code (including globals that are initialized from imported values).</li>
</ul>
van Rossum doesn&#8217;t like this approach much because the imports appear in a
strange place, but it does work.
Matthias Urlichs recommends restructuring your code so that the recursive import
is not necessary in the first place.
These solutions are not mutually exclusive.
</div>
<div class="section" id="import-x-y-z-returns-module-x-how-do-i-get-z">
<h3><a class="toc-backref" href="#id63">__import__(&#8216;x.y.z&#8217;) returns &lt;module &#8216;x&#8217;&gt;; how do I get z?</a><a class="headerlink" href="#import-x-y-z-returns-module-x-how-do-i-get-z" title="Permalink to this headline">¶</a></h3>
Try:
<div class="highlight-python"><div class="highlight"><pre>__import__(&#39;x.y.z&#39;).y.z
</pre></div>
</div>
For more realistic situations, you may have to do something like
<div class="highlight-python"><div class="highlight"><pre>m = __import__(s)
for i in s.split(&quot;.&quot;)[1:]:
 m = getattr(m, i)
</pre></div>
</div>
See <a class="reference internal" href="../library/importlib.html#module-importlib" title="importlib: Convenience wrappers for __import__"><tt class="xref py py-mod docutils literal">importlib</tt></a> for a convenience function called
<a class="reference internal" href="../library/importlib.html#importlib.import_module" title="importlib.import_module"><tt class="xref py py-func docutils literal">import_module()</tt></a>.
</div>
<div class="section" id="when-i-edit-an-imported-module-and-reimport-it-the-changes-don-t-show-up-why-does-this-happen">
<h3><a class="toc-backref" href="#id64">When I edit an imported module and reimport it, the changes don&#8217;t show up. Why does this happen?</a><a class="headerlink" href="#when-i-edit-an-imported-module-and-reimport-it-the-changes-don-t-show-up-why-does-this-happen" title="Permalink to this headline">¶</a></h3>
For reasons of efficiency as well as consistency, Python only reads the module
file on the first time a module is imported. If it didn&#8217;t, in a program
consisting of many modules where each one imports the same basic module, the
basic module would be parsed and re-parsed many times. To force rereading of a
changed module, do this:
<div class="highlight-python"><div class="highlight"><pre>import modname
reload(modname)
</pre></div>
</div>
Warning: this technique is not 100% fool-proof. In particular, modules
containing statements like
<div class="highlight-python"><div class="highlight"><pre>from modname import some_objects
</pre></div>
</div>
will continue to work with the old version of the imported objects. If the
module contains class definitions, existing class instances will not be
updated to use the new class definition. This can result in the following
paradoxical behaviour:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; import cls
&gt;&gt;&gt; c = cls.C() # Create an instance of C
&gt;&gt;&gt; reload(cls)
&lt;module &#39;cls&#39; from &#39;cls.pyc&#39;&gt;
&gt;&gt;&gt; isinstance(c, cls.C) # isinstance is false?!?
False
</pre></div>
</div>
The nature of the problem is made clear if you print out the class objects:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; c.__class__
&lt;class cls.C at 0x7352a0&gt;
&gt;&gt;&gt; cls.C
&lt;class cls.C at 0x4198d0&gt;
</pre></div>
</div>
</div>
</div>
</div>

</div>
 </div>
 </div>
 <div class="sphinxsidebar">
 <div class="sphinxsidebarwrapper">
 <h3><a href="../contents.html">Table Of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#">Programming FAQ</a><ul>
<li><a class="reference internal" href="#general-questions">General Questions</a></li>
<li><a class="reference internal" href="#core-language">Core Language</a></li>
<li><a class="reference internal" href="#numbers-and-strings">Numbers and strings</a></li>
<li><a class="reference internal" href="#sequences-tuples-lists">Sequences (Tuples/Lists)</a></li>
<li><a class="reference internal" href="#dictionaries">Dictionaries</a></li>
<li><a class="reference internal" href="#objects">Objects</a></li>
<li><a class="reference internal" href="#modules">Modules</a></li>
</ul>
</li>
</ul>

<h4>Previous topic</h4>
 <a href="general.html"
 title="previous chapter">General Python FAQ</a>
 <h4>Next topic</h4>
 <a href="design.html"
 title="next chapter">Design and History FAQ</a>
<h3>This Page</h3>
<ul class="this-page-menu">
 <li><a href="../bugs.html">Report a Bug</a></li>
 <li><a href="../_sources/faq/programming.txt"
 rel="nofollow">Show Source</a></li>
</ul>

<div id="searchbox" style="display: none">
 <h3>Quick search</h3>
 <form class="search" action="../search.html" method="get">
 <input type="text" name="q" />
 <input type="submit" value="Go" />
 <input type="hidden" name="check_keywords" value="yes" />
 <input type="hidden" name="area" value="default" />
 </form>
 
 Enter search terms or a module, class or function name.
 
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
 </div>
 </div>
 <div class="clearer"></div>
 </div>
 <div class="related">
 <h3>Navigation</h3>
 <ul>
 <li class="right" style="margin-right: 10px">
 <a href="../genindex.html" title="General Index"
 >index</a></li>
 <li class="right" >
 <a href="../py-modindex.html" title="Python Module Index"
 >modules</a> |</li>
 <li class="right" >
 <a href="design.html" title="Design and History FAQ"
 >next</a> |</li>
 <li class="right" >
 <a href="general.html" title="General Python FAQ"
 >previous</a> |</li>
 <li><img src="../_static/py.png" alt=""
 style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="http://www.python.org/">Python</a> &raquo;</li>
 <li>
 <a href="../index.html">Python 2.7.5 documentation</a> &raquo;
 </li>

<li><a href="index.html" >Python Frequently Asked Questions</a> &raquo;</li> 
 </ul>
 </div>
 <div class="footer">
 &copy; <a href="../copyright.html">Copyright</a> 1990-2019, Python Software Foundation.
 
 The Python Software Foundation is a non-profit corporation.
 <a href="http://www.python.org/psf/donations/">Please donate.</a>
 
 Last updated on Jul 03, 2019.
 <a href="../bugs.html">Found a bug</a>?
 
 Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.1.3.
 </div>

</body>
</html>

Cancel