Elepffwdsff

korsygfhrtzangaiide Elepffwdsff

<!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>What’s New in Python 2.5 &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="What’s New in Python" href="index.html" />
 <link rel="next" title="What’s New in Python 2.4" href="2.4.html" />
 <link rel="prev" title="What’s New in Python 2.6" href="2.6.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="2.4.html" title="What’s New in Python 2.4"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="2.6.html" title="What’s New in Python 2.6"
 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">What&#8217;s New in Python</a> &raquo;</li> 
 </ul>
 </div>

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body">
 
 <div class="section" id="what-s-new-in-python-2-5">
<h1>What&#8217;s New in Python 2.5<a class="headerlink" href="#what-s-new-in-python-2-5" title="Permalink to this headline">¶</a></h1>
<table class="docutils field-list" frame="void" rules="none">
<col class="field-name" />
<col class="field-body" />
<tbody valign="top">
<tr class="field-odd field"><th class="field-name">Author:</th><td class="field-body">A.M. Kuchling</td>
</tr>
</tbody>
</table>
This article explains the new features in Python 2.5. The final release of
Python 2.5 is scheduled for August 2006; <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0356">PEP 356</a> describes the planned
release schedule.
The changes in Python 2.5 are an interesting mix of language and library
improvements. The library enhancements will be more important to Python&#8217;s user
community, I think, because several widely-useful packages were added. New
modules include ElementTree for XML processing (<tt class="xref py py-mod docutils literal">xml.etree</tt>),
the SQLite database module (<tt class="xref py py-mod docutils literal">sqlite</tt>), and the <a class="reference internal" href="../library/ctypes.html#module-ctypes" title="ctypes: A foreign function library for Python."><tt class="xref py py-mod docutils literal">ctypes</tt></a>
module for calling C functions.
The language changes are of middling significance. Some pleasant new features
were added, but most of them aren&#8217;t features that you&#8217;ll use every day.
Conditional expressions were finally added to the language using a novel syntax;
see section <a class="reference internal" href="#pep-308">PEP 308: Conditional Expressions</a>. The new &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement will make
writing cleanup code easier (section <a class="reference internal" href="#pep-343">PEP 343: The &#8216;with&#8217; statement</a>). Values can now be passed
into generators (section <a class="reference internal" href="#pep-342">PEP 342: New Generator Features</a>). Imports are now visible as either
absolute or relative (section <a class="reference internal" href="#pep-328">PEP 328: Absolute and Relative Imports</a>). Some corner cases of exception
handling are handled better (section <a class="reference internal" href="#pep-341">PEP 341: Unified try/except/finally</a>). All these improvements
are worthwhile, but they&#8217;re improvements to one specific language feature or
another; none of them are broad modifications to Python&#8217;s semantics.
As well as the language and library additions, other improvements and bugfixes
were made throughout the source tree. A search through the SVN change logs
finds there were 353 patches applied and 458 bugs fixed between Python 2.4 and
2.5. (Both figures are likely to be underestimates.)
This article doesn&#8217;t try to be a complete specification of the new features;
instead changes are briefly introduced using helpful examples. For full
details, you should always refer to the documentation for Python 2.5 at
<a class="reference external" href="http://docs.python.org">http://docs.python.org</a>. If you want to understand the complete implementation
and design rationale, refer to the PEP for a particular new feature.
Comments, suggestions, and error reports for this document are welcome; please
e-mail them to the author or open a bug in the Python bug tracker.
<div class="section" id="pep-308-conditional-expressions">
<h2>PEP 308: Conditional Expressions<a class="headerlink" href="#pep-308-conditional-expressions" title="Permalink to this headline">¶</a></h2>
For a long time, people have been requesting a way to write conditional
expressions, which are expressions that return value A or value B depending on
whether a Boolean value is true or false. A conditional expression lets you
write a single assignment statement that has the same effect as the following:
<div class="highlight-python"><div class="highlight"><pre>if condition:
 x = true_value
else:
 x = false_value
</pre></div>
</div>
There have been endless tedious discussions of syntax on both python-dev and
comp.lang.python. A vote was even held that found the majority of voters wanted
conditional expressions in some form, but there was no syntax that was preferred
by a clear majority. Candidates included C&#8217;s <tt class="docutils literal">cond ? true_v : false_v</tt>, <tt class="docutils literal">if
cond then true_v else false_v</tt>, and 16 other variations.
Guido van Rossum eventually chose a surprising syntax:
<div class="highlight-python"><div class="highlight"><pre>x = true_value if condition else false_value
</pre></div>
</div>
Evaluation is still lazy as in existing Boolean expressions, so the order of
evaluation jumps around a bit. The condition expression in the middle is
evaluated first, and the true_value expression is evaluated only if the
condition was true. Similarly, the false_value expression is only evaluated
when the condition is false.
This syntax may seem strange and backwards; why does the condition go in the
middle of the expression, and not in the front as in C&#8217;s <tt class="docutils literal">c ? x : y</tt>? The
decision was checked by applying the new syntax to the modules in the standard
library and seeing how the resulting code read. In many cases where a
conditional expression is used, one value seems to be the &#8216;common case&#8217; and one
value is an &#8216;exceptional case&#8217;, used only on rarer occasions when the condition
isn&#8217;t met. The conditional syntax makes this pattern a bit more obvious:
<div class="highlight-python"><div class="highlight"><pre>contents = ((doc + &#39;\n&#39;) if doc else &#39;&#39;)
</pre></div>
</div>
I read the above statement as meaning &#8220;here contents is usually assigned a
value of <tt class="docutils literal">doc+'\n'</tt>; sometimes doc is empty, in which special case an empty
string is returned.&#8221; I doubt I will use conditional expressions very often
where there isn&#8217;t a clear common and uncommon case.
There was some discussion of whether the language should require surrounding
conditional expressions with parentheses. The decision was made to not
require parentheses in the Python language&#8217;s grammar, but as a matter of style I
think you should always use them. Consider these two statements:
<div class="highlight-python"><div class="highlight"><pre># First version -- no parens
level = 1 if logging else 0

# Second version -- with parens
level = (1 if logging else 0)
</pre></div>
</div>
In the first version, I think a reader&#8217;s eye might group the statement into
&#8216;level = 1&#8217;, &#8216;if logging&#8217;, &#8216;else 0&#8217;, and think that the condition decides
whether the assignment to level is performed. The second version reads
better, in my opinion, because it makes it clear that the assignment is always
performed and the choice is being made between two values.
Another reason for including the brackets: a few odd combinations of list
comprehensions and lambdas could look like incorrect conditional expressions.
See <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0308">PEP 308</a> for some examples. If you put parentheses around your
conditional expressions, you won&#8217;t run into this case.
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0308">PEP 308</a> - Conditional Expressions</dt>
<dd>PEP written by Guido van Rossum and Raymond D. Hettinger; implemented by Thomas
Wouters.</dd>
</dl>
</div>
</div>
<div class="section" id="pep-309-partial-function-application">
<h2>PEP 309: Partial Function Application<a class="headerlink" href="#pep-309-partial-function-application" title="Permalink to this headline">¶</a></h2>
The <a class="reference internal" href="../library/functools.html#module-functools" title="functools: Higher-order functions and operations on callable objects."><tt class="xref py py-mod docutils literal">functools</tt></a> module is intended to contain tools for functional-style
programming.
One useful tool in this module is the <tt class="xref py py-func docutils literal">partial()</tt> function. For programs
written in a functional style, you&#8217;ll sometimes want to construct variants of
existing functions that have some of the parameters filled in. Consider a
Python function <tt class="docutils literal">f(a, b, c)</tt>; you could create a new function <tt class="docutils literal">g(b, c)</tt> that
was equivalent to <tt class="docutils literal">f(1, b, c)</tt>. This is called &#8220;partial function
application&#8221;.
<tt class="xref py py-func docutils literal">partial()</tt> takes the arguments <tt class="docutils literal">(function, arg1, arg2, ... kwarg1=value1,
kwarg2=value2)</tt>. The resulting object is callable, so you can just call it to
invoke function with the filled-in arguments.
Here&#8217;s a small but realistic example:
<div class="highlight-python"><div class="highlight"><pre>import functools

def log (message, subsystem):
 &quot;Write the contents of &#39;message&#39; to the specified subsystem.&quot;
 print &#39;%s: %s&#39; % (subsystem, message)
 ...

server_log = functools.partial(log, subsystem=&#39;server&#39;)
server_log(&#39;Unable to open socket&#39;)
</pre></div>
</div>
Here&#8217;s another example, from a program that uses PyGTK. Here a context-
sensitive pop-up menu is being constructed dynamically. The callback provided
for the menu option is a partially applied version of the <tt class="xref py py-meth docutils literal">open_item()</tt>
method, where the first argument has been provided.
<div class="highlight-python"><div class="highlight"><pre>...
class Application:
 def open_item(self, path):
 ...
 def init (self):
 open_func = functools.partial(self.open_item, item_path)
 popup_menu.append( (&quot;Open&quot;, open_func, 1) )
</pre></div>
</div>
Another function in the <a class="reference internal" href="../library/functools.html#module-functools" title="functools: Higher-order functions and operations on callable objects."><tt class="xref py py-mod docutils literal">functools</tt></a> module is the
<tt class="xref py py-func docutils literal">update_wrapper(wrapper, wrapped)()</tt> function that helps you write well-
behaved decorators. <tt class="xref py py-func docutils literal">update_wrapper()</tt> copies the name, module, and
docstring attribute to a wrapper function so that tracebacks inside the wrapped
function are easier to understand. For example, you might write:
<div class="highlight-python"><div class="highlight"><pre>def my_decorator(f):
 def wrapper(*args, **kwds):
 print &#39;Calling decorated function&#39;
 return f(*args, **kwds)
 functools.update_wrapper(wrapper, f)
 return wrapper
</pre></div>
</div>
<tt class="xref py py-func docutils literal">wraps()</tt> is a decorator that can be used inside your own decorators to copy
the wrapped function&#8217;s information. An alternate version of the previous
example would be:
<div class="highlight-python"><div class="highlight"><pre>def my_decorator(f):
 @functools.wraps(f)
 def wrapper(*args, **kwds):
 print &#39;Calling decorated function&#39;
 return f(*args, **kwds)
 return wrapper
</pre></div>
</div>
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0309">PEP 309</a> - Partial Function Application</dt>
<dd>PEP proposed and written by Peter Harris; implemented by Hye-Shik Chang and Nick
Coghlan, with adaptations by Raymond Hettinger.</dd>
</dl>
</div>
</div>
<div class="section" id="pep-314-metadata-for-python-software-packages-v1-1">
<h2>PEP 314: Metadata for Python Software Packages v1.1<a class="headerlink" href="#pep-314-metadata-for-python-software-packages-v1-1" title="Permalink to this headline">¶</a></h2>
Some simple dependency support was added to Distutils. The <tt class="xref py py-func docutils literal">setup()</tt>
function now has <tt class="docutils literal">requires</tt>, <tt class="docutils literal">provides</tt>, and <tt class="docutils literal">obsoletes</tt> keyword
parameters. When you build a source distribution using the <tt class="docutils literal">sdist</tt> command,
the dependency information will be recorded in the <tt class="file docutils literal">PKG-INFO</tt> file.
Another new keyword parameter is <tt class="docutils literal">download_url</tt>, which should be set to a URL
for the package&#8217;s source code. This means it&#8217;s now possible to look up an entry
in the package index, determine the dependencies for a package, and download the
required packages.
<div class="highlight-python"><pre>VERSION = '1.0'
setup(name='PyPackage',
 version=VERSION,
 requires=['numarray', 'zlib (&gt;=1.1.4)'],
 obsoletes=['OldPackage']
 download_url=('http://www.example.com/pypackage/dist/pkg-%s.tar.gz'
 % VERSION),
 )</pre>
</div>
Another new enhancement to the Python package index at
<a class="reference external" href="http://cheeseshop.python.org">http://cheeseshop.python.org</a> is storing source and binary archives for a
package. The new upload Distutils command will upload a package to
the repository.
Before a package can be uploaded, you must be able to build a distribution using
the sdist Distutils command. Once that works, you can run <tt class="docutils literal">python
setup.py upload</tt> to add your package to the PyPI archive. Optionally you can
GPG-sign the package by supplying the --sign and --identity
options.
Package uploading was implemented by Martin von Löwis and Richard Jones.
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0314">PEP 314</a> - Metadata for Python Software Packages v1.1</dt>
<dd>PEP proposed and written by A.M. Kuchling, Richard Jones, and Fred Drake;
implemented by Richard Jones and Fred Drake.</dd>
</dl>
</div>
</div>
<div class="section" id="pep-328-absolute-and-relative-imports">
<h2>PEP 328: Absolute and Relative Imports<a class="headerlink" href="#pep-328-absolute-and-relative-imports" title="Permalink to this headline">¶</a></h2>
The simpler part of PEP 328 was implemented in Python 2.4: parentheses could now
be used to enclose the names imported from a module using the <tt class="docutils literal">from ... import
...</tt> statement, making it easier to import many different names.
The more complicated part has been implemented in Python 2.5: importing a module
can be specified to use absolute or package-relative imports. The plan is to
move toward making absolute imports the default in future versions of Python.
Let&#8217;s say you have a package directory like this:
<div class="highlight-python"><pre>pkg/
pkg/__init__.py
pkg/main.py
pkg/string.py</pre>
</div>
This defines a package named <tt class="xref py py-mod docutils literal">pkg</tt> containing the <tt class="xref py py-mod docutils literal">pkg.main</tt> and
<tt class="xref py py-mod docutils literal">pkg.string</tt> submodules.
Consider the code in the <tt class="file docutils literal">main.py</tt> module. What happens if it executes
the statement <tt class="docutils literal">import string</tt>? In Python 2.4 and earlier, it will first look
in the package&#8217;s directory to perform a relative import, finds
<tt class="file docutils literal">pkg/string.py</tt>, imports the contents of that file as the
<tt class="xref py py-mod docutils literal">pkg.string</tt> module, and that module is bound to the name <tt class="docutils literal">string</tt> in the
<tt class="xref py py-mod docutils literal">pkg.main</tt> module&#8217;s namespace.
That&#8217;s fine if <tt class="xref py py-mod docutils literal">pkg.string</tt> was what you wanted. But what if you wanted
Python&#8217;s standard <a class="reference internal" href="../library/string.html#module-string" title="string: Common string operations."><tt class="xref py py-mod docutils literal">string</tt></a> module? There&#8217;s no clean way to ignore
<tt class="xref py py-mod docutils literal">pkg.string</tt> and look for the standard module; generally you had to look at
the contents of <tt class="docutils literal">sys.modules</tt>, which is slightly unclean. Holger Krekel&#8217;s
<tt class="xref py py-mod docutils literal">py.std</tt> package provides a tidier way to perform imports from the standard
library, <tt class="docutils literal">import py ; py.std.string.join()</tt>, but that package isn&#8217;t available
on all Python installations.
Reading code which relies on relative imports is also less clear, because a
reader may be confused about which module, <a class="reference internal" href="../library/string.html#module-string" title="string: Common string operations."><tt class="xref py py-mod docutils literal">string</tt></a> or <tt class="xref py py-mod docutils literal">pkg.string</tt>,
is intended to be used. Python users soon learned not to duplicate the names of
standard library modules in the names of their packages&#8217; submodules, but you
can&#8217;t protect against having your submodule&#8217;s name being used for a new module
added in a future version of Python.
In Python 2.5, you can switch <a class="reference internal" href="../reference/simple_stmts.html#import"><tt class="xref std std-keyword docutils literal">import</tt></a>&#8216;s behaviour to absolute imports
using a <tt class="docutils literal">from __future__ import absolute_import</tt> directive. This absolute-
import behaviour will become the default in a future version (probably Python
2.7). Once absolute imports are the default, <tt class="docutils literal">import string</tt> will always
find the standard library&#8217;s version. It&#8217;s suggested that users should begin
using absolute imports as much as possible, so it&#8217;s preferable to begin writing
<tt class="docutils literal">from pkg import string</tt> in your code.
Relative imports are still possible by adding a leading period to the module
name when using the <tt class="docutils literal">from ... import</tt> form:
<div class="highlight-python"><div class="highlight"><pre># Import names from pkg.string
from .string import name1, name2
# Import pkg.string
from . import string
</pre></div>
</div>
This imports the <a class="reference internal" href="../library/string.html#module-string" title="string: Common string operations."><tt class="xref py py-mod docutils literal">string</tt></a> module relative to the current package, so in
<tt class="xref py py-mod docutils literal">pkg.main</tt> this will import name1 and name2 from <tt class="xref py py-mod docutils literal">pkg.string</tt>.
Additional leading periods perform the relative import starting from the parent
of the current package. For example, code in the <tt class="xref py py-mod docutils literal">A.B.C</tt> module can do:
<div class="highlight-python"><div class="highlight"><pre>from . import D # Imports A.B.D
from .. import E # Imports A.E
from ..F import G # Imports A.F.G
</pre></div>
</div>
Leading periods cannot be used with the <tt class="docutils literal">import modname</tt> form of the import
statement, only the <tt class="docutils literal">from ... import</tt> form.
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0328">PEP 328</a> - Imports: Multi-Line and Absolute/Relative</dt>
<dd>PEP written by Aahz; implemented by Thomas Wouters.</dd>
<dt><a class="reference external" href="http://codespeak.net/py/current/doc/index.html">http://codespeak.net/py/current/doc/index.html</a></dt>
<dd>The py library by Holger Krekel, which contains the <tt class="xref py py-mod docutils literal">py.std</tt> package.</dd>
</dl>
</div>
</div>
<div class="section" id="pep-338-executing-modules-as-scripts">
<h2>PEP 338: Executing Modules as Scripts<a class="headerlink" href="#pep-338-executing-modules-as-scripts" title="Permalink to this headline">¶</a></h2>
The <a class="reference internal" href="../using/cmdline.html#cmdoption-m">-m</a> switch added in Python 2.4 to execute a module as a script
gained a few more abilities. Instead of being implemented in C code inside the
Python interpreter, the switch now uses an implementation in a new module,
<a class="reference internal" href="../library/runpy.html#module-runpy" title="runpy: Locate and run Python modules without importing them first."><tt class="xref py py-mod docutils literal">runpy</tt></a>.
The <a class="reference internal" href="../library/runpy.html#module-runpy" title="runpy: Locate and run Python modules without importing them first."><tt class="xref py py-mod docutils literal">runpy</tt></a> module implements a more sophisticated import mechanism so that
it&#8217;s now possible to run modules in a package such as <tt class="xref py py-mod docutils literal">pychecker.checker</tt>.
The module also supports alternative import mechanisms such as the
<a class="reference internal" href="../library/zipimport.html#module-zipimport" title="zipimport: support for importing Python modules from ZIP archives."><tt class="xref py py-mod docutils literal">zipimport</tt></a> module. This means you can add a .zip archive&#8217;s path to
<tt class="docutils literal">sys.path</tt> and then use the <a class="reference internal" href="../using/cmdline.html#cmdoption-m">-m</a> switch to execute code from the
archive.
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0338">PEP 338</a> - Executing modules as scripts</dt>
<dd>PEP written and implemented by Nick Coghlan.</dd>
</dl>
</div>
</div>
<div class="section" id="pep-341-unified-try-except-finally">
<h2>PEP 341: Unified try/except/finally<a class="headerlink" href="#pep-341-unified-try-except-finally" title="Permalink to this headline">¶</a></h2>
Until Python 2.5, the <a class="reference internal" href="../reference/compound_stmts.html#try"><tt class="xref std std-keyword docutils literal">try</tt></a> statement came in two flavours. You could
use a <a class="reference internal" href="../reference/compound_stmts.html#finally"><tt class="xref std std-keyword docutils literal">finally</tt></a> block to ensure that code is always executed, or one or
more <a class="reference internal" href="../reference/compound_stmts.html#except"><tt class="xref std std-keyword docutils literal">except</tt></a> blocks to catch specific exceptions. You couldn&#8217;t
combine both <a class="reference internal" href="../reference/compound_stmts.html#except"><tt class="xref std std-keyword docutils literal">except</tt></a> blocks and a <a class="reference internal" href="../reference/compound_stmts.html#finally"><tt class="xref std std-keyword docutils literal">finally</tt></a> block, because
generating the right bytecode for the combined version was complicated and it
wasn&#8217;t clear what the semantics of the combined statement should be.
Guido van Rossum spent some time working with Java, which does support the
equivalent of combining <a class="reference internal" href="../reference/compound_stmts.html#except"><tt class="xref std std-keyword docutils literal">except</tt></a> blocks and a <a class="reference internal" href="../reference/compound_stmts.html#finally"><tt class="xref std std-keyword docutils literal">finally</tt></a> block,
and this clarified what the statement should mean. In Python 2.5, you can now
write:
<div class="highlight-python"><pre>try:
 block-1 ...
except Exception1:
 handler-1 ...
except Exception2:
 handler-2 ...
else:
 else-block
finally:
 final-block</pre>
</div>
The code in block-1 is executed. If the code raises an exception, the various
<a class="reference internal" href="../reference/compound_stmts.html#except"><tt class="xref std std-keyword docutils literal">except</tt></a> blocks are tested: if the exception is of class
<tt class="xref py py-class docutils literal">Exception1</tt>, handler-1 is executed; otherwise if it&#8217;s of class
<tt class="xref py py-class docutils literal">Exception2</tt>, handler-2 is executed, and so forth. If no exception is
raised, the else-block is executed.
No matter what happened previously, the final-block is executed once the code
block is complete and any raised exceptions handled. Even if there&#8217;s an error in
an exception handler or the else-block and a new exception is raised, the code
in the final-block is still run.
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0341">PEP 341</a> - Unifying try-except and try-finally</dt>
<dd>PEP written by Georg Brandl; implementation by Thomas Lee.</dd>
</dl>
</div>
</div>
<div class="section" id="pep-342-new-generator-features">
<h2>PEP 342: New Generator Features<a class="headerlink" href="#pep-342-new-generator-features" title="Permalink to this headline">¶</a></h2>
Python 2.5 adds a simple way to pass values into a generator. As introduced in
Python 2.3, generators only produce output; once a generator&#8217;s code was invoked
to create an iterator, there was no way to pass any new information into the
function when its execution is resumed. Sometimes the ability to pass in some
information would be useful. Hackish solutions to this include making the
generator&#8217;s code look at a global variable and then changing the global
variable&#8217;s value, or passing in some mutable object that callers then modify.
To refresh your memory of basic generators, here&#8217;s a simple example:
<div class="highlight-python"><div class="highlight"><pre>def counter (maximum):
 i = 0
 while i &lt; maximum:
 yield i
 i += 1
</pre></div>
</div>
When you call <tt class="docutils literal">counter(10)</tt>, the result is an iterator that returns the values
from 0 up to 9. On encountering the <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> statement, the iterator
returns the provided value and suspends the function&#8217;s execution, preserving the
local variables. Execution resumes on the following call to the iterator&#8217;s
<a class="reference internal" href="../library/functions.html#next" title="next"><tt class="xref py py-meth docutils literal">next()</tt></a> method, picking up after the <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> statement.
In Python 2.3, <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> was a statement; it didn&#8217;t return any value. In
2.5, <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> is now an expression, returning a value that can be
assigned to a variable or otherwise operated on:
<div class="highlight-python"><div class="highlight"><pre>val = (yield i)
</pre></div>
</div>
I recommend that you always put parentheses around a <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> expression
when you&#8217;re doing something with the returned value, as in the above example.
The parentheses aren&#8217;t always necessary, but it&#8217;s easier to always add them
instead of having to remember when they&#8217;re needed.
(<a class="pep reference external" href="http://www.python.org/dev/peps/pep-0342">PEP 342</a> explains the exact rules, which are that a <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a>-expression must always be parenthesized except when it occurs at the top-level
expression on the right-hand side of an assignment. This means you can write
<tt class="docutils literal">val = yield i</tt> but have to use parentheses when there&#8217;s an operation, as in
<tt class="docutils literal">val = (yield i) + 12</tt>.)
Values are sent into a generator by calling its <tt class="xref py py-meth docutils literal">send(value)()</tt> method. The
generator&#8217;s code is then resumed and the <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> expression returns the
specified value. If the regular <a class="reference internal" href="../library/functions.html#next" title="next"><tt class="xref py py-meth docutils literal">next()</tt></a> method is called, the
<a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> returns <a class="reference internal" href="../library/constants.html#None" title="None"><tt class="xref py py-const docutils literal">None</tt></a>.
Here&#8217;s the previous example, modified to allow changing the value of the
internal counter.
<div class="highlight-python"><div class="highlight"><pre>def counter (maximum):
 i = 0
 while i &lt; maximum:
 val = (yield i)
 # If value provided, change counter
 if val is not None:
 i = val
 else:
 i += 1
</pre></div>
</div>
And here&#8217;s an example of changing the counter:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; it = counter(10)
&gt;&gt;&gt; print it.next()
0
&gt;&gt;&gt; print it.next()
1
&gt;&gt;&gt; print it.send(8)
8
&gt;&gt;&gt; print it.next()
9
&gt;&gt;&gt; print it.next()
Traceback (most recent call last):
 File &quot;t.py&quot;, line 15, in ?
 print it.next()
StopIteration
</pre></div>
</div>
<a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> will usually return <a class="reference internal" href="../library/constants.html#None" title="None"><tt class="xref py py-const docutils literal">None</tt></a>, so you should always check
for this case. Don&#8217;t just use its value in expressions unless you&#8217;re sure that
the <tt class="xref py py-meth docutils literal">send()</tt> method will be the only method used to resume your generator
function.
In addition to <tt class="xref py py-meth docutils literal">send()</tt>, there are two other new methods on generators:
<ul>
<li><tt class="xref py py-meth docutils literal">throw(type, value=None, traceback=None)()</tt> is used to raise an exception
inside the generator; the exception is raised by the <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> expression
where the generator&#8217;s execution is paused.
</li>
<li><tt class="xref py py-meth docutils literal">close()</tt> raises a new <a class="reference internal" href="../library/exceptions.html#exceptions.GeneratorExit" title="exceptions.GeneratorExit"><tt class="xref py py-exc docutils literal">GeneratorExit</tt></a> exception inside the generator
to terminate the iteration. On receiving this exception, the generator&#8217;s code
must either raise <a class="reference internal" href="../library/exceptions.html#exceptions.GeneratorExit" title="exceptions.GeneratorExit"><tt class="xref py py-exc docutils literal">GeneratorExit</tt></a> or <a class="reference internal" href="../library/exceptions.html#exceptions.StopIteration" title="exceptions.StopIteration"><tt class="xref py py-exc docutils literal">StopIteration</tt></a>. Catching the
<a class="reference internal" href="../library/exceptions.html#exceptions.GeneratorExit" title="exceptions.GeneratorExit"><tt class="xref py py-exc docutils literal">GeneratorExit</tt></a> exception and returning a value is illegal and will trigger
a <a class="reference internal" href="../library/exceptions.html#exceptions.RuntimeError" title="exceptions.RuntimeError"><tt class="xref py py-exc docutils literal">RuntimeError</tt></a>; if the function raises some other exception, that
exception is propagated to the caller. <tt class="xref py py-meth docutils literal">close()</tt> will also be called by
Python&#8217;s garbage collector when the generator is garbage-collected.
If you need to run cleanup code when a <a class="reference internal" href="../library/exceptions.html#exceptions.GeneratorExit" title="exceptions.GeneratorExit"><tt class="xref py py-exc docutils literal">GeneratorExit</tt></a> occurs, I suggest
using a <tt class="docutils literal">try: ... finally:</tt> suite instead of catching <a class="reference internal" href="../library/exceptions.html#exceptions.GeneratorExit" title="exceptions.GeneratorExit"><tt class="xref py py-exc docutils literal">GeneratorExit</tt></a>.
</li>
</ul>
The cumulative effect of these changes is to turn generators from one-way
producers of information into both producers and consumers.
Generators also become coroutines, a more generalized form of subroutines.
Subroutines are entered at one point and exited at another point (the top of the
function, and a <a class="reference internal" href="../reference/simple_stmts.html#return"><tt class="xref std std-keyword docutils literal">return</tt></a> statement), but coroutines can be entered,
exited, and resumed at many different points (the <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> statements).
We&#8217;ll have to figure out patterns for using coroutines effectively in Python.
The addition of the <tt class="xref py py-meth docutils literal">close()</tt> method has one side effect that isn&#8217;t obvious.
<tt class="xref py py-meth docutils literal">close()</tt> is called when a generator is garbage-collected, so this means the
generator&#8217;s code gets one last chance to run before the generator is destroyed.
This last chance means that <tt class="docutils literal">try...finally</tt> statements in generators can now
be guaranteed to work; the <a class="reference internal" href="../reference/compound_stmts.html#finally"><tt class="xref std std-keyword docutils literal">finally</tt></a> clause will now always get a
chance to run. The syntactic restriction that you couldn&#8217;t mix <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a>
statements with a <tt class="docutils literal">try...finally</tt> suite has therefore been removed. This
seems like a minor bit of language trivia, but using generators and
<tt class="docutils literal">try...finally</tt> is actually necessary in order to implement the
<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a> statement described by PEP 343. I&#8217;ll look at this new statement
in the following section.
Another even more esoteric effect of this change: previously, the
<tt class="xref py py-attr docutils literal">gi_frame</tt> attribute of a generator was always a frame object. It&#8217;s now
possible for <tt class="xref py py-attr docutils literal">gi_frame</tt> to be <tt class="docutils literal">None</tt> once the generator has been
exhausted.
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0342">PEP 342</a> - Coroutines via Enhanced Generators</dt>
<dd>PEP written by Guido van Rossum and Phillip J. Eby; implemented by Phillip J.
Eby. Includes examples of some fancier uses of generators as coroutines.
Earlier versions of these features were proposed in <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0288">PEP 288</a> by Raymond
Hettinger and <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0325">PEP 325</a> by Samuele Pedroni.
</dd>
<dt><a class="reference external" href="http://en.wikipedia.org/wiki/Coroutine">http://en.wikipedia.org/wiki/Coroutine</a></dt>
<dd>The Wikipedia entry for coroutines.</dd>
<dt><a class="reference external" href="http://www.sidhe.org/~dan/blog/archives/000178.html">http://www.sidhe.org/~dan/blog/archives/000178.html</a></dt>
<dd>An explanation of coroutines from a Perl point of view, written by Dan Sugalski.</dd>
</dl>
</div>
</div>
<div class="section" id="pep-343-the-with-statement">
<h2>PEP 343: The &#8216;with&#8217; statement<a class="headerlink" href="#pep-343-the-with-statement" title="Permalink to this headline">¶</a></h2>
The &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement clarifies code that previously would use
<tt class="docutils literal">try...finally</tt> blocks to ensure that clean-up code is executed. In this
section, I&#8217;ll discuss the statement as it will commonly be used. In the next
section, I&#8217;ll examine the implementation details and show how to write objects
for use with this statement.
The &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement is a new control-flow structure whose basic
structure is:
<div class="highlight-python"><pre>with expression [as variable]:
 with-block</pre>
</div>
The expression is evaluated, and it should result in an object that supports the
context management protocol (that is, has <a class="reference internal" href="../reference/datamodel.html#object.__enter__" title="object.__enter__"><tt class="xref py py-meth docutils literal">__enter__()</tt></a> and <a class="reference internal" href="../reference/datamodel.html#object.__exit__" title="object.__exit__"><tt class="xref py py-meth docutils literal">__exit__()</tt></a>
methods.
The object&#8217;s <a class="reference internal" href="../reference/datamodel.html#object.__enter__" title="object.__enter__"><tt class="xref py py-meth docutils literal">__enter__()</tt></a> is called before with-block is executed and
therefore can run set-up code. It also may return a value that is bound to the
name variable, if given. (Note carefully that variable is not assigned
the result of expression.)
After execution of the with-block is finished, the object&#8217;s <a class="reference internal" href="../reference/datamodel.html#object.__exit__" title="object.__exit__"><tt class="xref py py-meth docutils literal">__exit__()</tt></a>
method is called, even if the block raised an exception, and can therefore run
clean-up code.
To enable the statement in Python 2.5, you need to add the following directive
to your module:
<div class="highlight-python"><div class="highlight"><pre>from __future__ import with_statement
</pre></div>
</div>
The statement will always be enabled in Python 2.6.
Some standard Python objects now support the context management protocol and can
be used with the &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement. File objects are one example:
<div class="highlight-python"><div class="highlight"><pre>with open(&#39;/etc/passwd&#39;, &#39;r&#39;) as f:
 for line in f:
 print line
 ... more processing code ...
</pre></div>
</div>
After this statement has executed, the file object in f will have been
automatically closed, even if the <a class="reference internal" href="../reference/compound_stmts.html#for"><tt class="xref std std-keyword docutils literal">for</tt></a> loop raised an exception part-
way through the block.
<div class="admonition note">
Note
In this case, f is the same object created by <a class="reference internal" href="../library/functions.html#open" title="open"><tt class="xref py py-func docutils literal">open()</tt></a>, because
<tt class="xref py py-meth docutils literal">file.__enter__()</tt> returns self.
</div>
The <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> module&#8217;s locks and condition variables also support the
&#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement:
<div class="highlight-python"><div class="highlight"><pre>lock = threading.Lock()
with lock:
 # Critical section of code
 ...
</pre></div>
</div>
The lock is acquired before the block is executed and always released once the
block is complete.
The new <tt class="xref py py-func docutils literal">localcontext()</tt> function in the <a class="reference internal" href="../library/decimal.html#module-decimal" title="decimal: Implementation of the General Decimal Arithmetic Specification."><tt class="xref py py-mod docutils literal">decimal</tt></a> module makes it easy
to save and restore the current decimal context, which encapsulates the desired
precision and rounding characteristics for computations:
<div class="highlight-python"><div class="highlight"><pre>from decimal import Decimal, Context, localcontext

# Displays with default precision of 28 digits
v = Decimal(&#39;578&#39;)
print v.sqrt()

with localcontext(Context(prec=16)):
 # All code in this block uses a precision of 16 digits.
 # The original context is restored on exiting the block.
 print v.sqrt()
</pre></div>
</div>
<div class="section" id="writing-context-managers">
<h3>Writing Context Managers<a class="headerlink" href="#writing-context-managers" title="Permalink to this headline">¶</a></h3>
Under the hood, the &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement is fairly complicated. Most
people will only use &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; in company with existing objects and
don&#8217;t need to know these details, so you can skip the rest of this section if
you like. Authors of new objects will need to understand the details of the
underlying implementation and should keep reading.
A high-level explanation of the context management protocol is:
<ul class="simple">
<li>The expression is evaluated and should result in an object called a &#8220;context
manager&#8221;. The context manager must have <a class="reference internal" href="../reference/datamodel.html#object.__enter__" title="object.__enter__"><tt class="xref py py-meth docutils literal">__enter__()</tt></a> and <a class="reference internal" href="../reference/datamodel.html#object.__exit__" title="object.__exit__"><tt class="xref py py-meth docutils literal">__exit__()</tt></a>
methods.</li>
<li>The context manager&#8217;s <a class="reference internal" href="../reference/datamodel.html#object.__enter__" title="object.__enter__"><tt class="xref py py-meth docutils literal">__enter__()</tt></a> method is called. The value returned
is assigned to VAR. If no <tt class="docutils literal">'as VAR'</tt> clause is present, the value is simply
discarded.</li>
<li>The code in BLOCK is executed.</li>
<li>If BLOCK raises an exception, the <tt class="xref py py-meth docutils literal">__exit__(type, value, traceback)()</tt>
is called with the exception details, the same values returned by
<a class="reference internal" href="../library/sys.html#sys.exc_info" title="sys.exc_info"><tt class="xref py py-func docutils literal">sys.exc_info()</tt></a>. The method&#8217;s return value controls whether the exception
is re-raised: any false value re-raises the exception, and <tt class="docutils literal">True</tt> will result
in suppressing it. You&#8217;ll only rarely want to suppress the exception, because
if you do the author of the code containing the &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement will
never realize anything went wrong.</li>
<li>If BLOCK didn&#8217;t raise an exception, the <a class="reference internal" href="../reference/datamodel.html#object.__exit__" title="object.__exit__"><tt class="xref py py-meth docutils literal">__exit__()</tt></a> method is still
called, but type, value, and traceback are all <tt class="docutils literal">None</tt>.</li>
</ul>
Let&#8217;s think through an example. I won&#8217;t present detailed code but will only
sketch the methods necessary for a database that supports transactions.
(For people unfamiliar with database terminology: a set of changes to the
database are grouped into a transaction. Transactions can be either committed,
meaning that all the changes are written into the database, or rolled back,
meaning that the changes are all discarded and the database is unchanged. See
any database textbook for more information.)
Let&#8217;s assume there&#8217;s an object representing a database connection. Our goal will
be to let the user write code like this:
<div class="highlight-python"><div class="highlight"><pre>db_connection = DatabaseConnection()
with db_connection as cursor:
 cursor.execute(&#39;insert into ...&#39;)
 cursor.execute(&#39;delete from ...&#39;)
 # ... more operations ...
</pre></div>
</div>
The transaction should be committed if the code in the block runs flawlessly or
rolled back if there&#8217;s an exception. Here&#8217;s the basic interface for
<tt class="xref py py-class docutils literal">DatabaseConnection</tt> that I&#8217;ll assume:
<div class="highlight-python"><div class="highlight"><pre>class DatabaseConnection:
 # Database interface
 def cursor (self):
 &quot;Returns a cursor object and starts a new transaction&quot;
 def commit (self):
 &quot;Commits current transaction&quot;
 def rollback (self):
 &quot;Rolls back current transaction&quot;
</pre></div>
</div>
The <a class="reference internal" href="../reference/datamodel.html#object.__enter__" title="object.__enter__"><tt class="xref py py-meth docutils literal">__enter__()</tt></a> method is pretty easy, having only to start a new
transaction. For this application the resulting cursor object would be a useful
result, so the method will return it. The user can then add <tt class="docutils literal">as cursor</tt> to
their &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement to bind the cursor to a variable name.
<div class="highlight-python"><div class="highlight"><pre>class DatabaseConnection:
 ...
 def __enter__ (self):
 # Code to start a new transaction
 cursor = self.cursor()
 return cursor
</pre></div>
</div>
The <a class="reference internal" href="../reference/datamodel.html#object.__exit__" title="object.__exit__"><tt class="xref py py-meth docutils literal">__exit__()</tt></a> method is the most complicated because it&#8217;s where most of
the work has to be done. The method has to check if an exception occurred. If
there was no exception, the transaction is committed. The transaction is rolled
back if there was an exception.
In the code below, execution will just fall off the end of the function,
returning the default value of <tt class="docutils literal">None</tt>. <tt class="docutils literal">None</tt> is false, so the exception
will be re-raised automatically. If you wished, you could be more explicit and
add a <a class="reference internal" href="../reference/simple_stmts.html#return"><tt class="xref std std-keyword docutils literal">return</tt></a> statement at the marked location.
<div class="highlight-python"><div class="highlight"><pre>class DatabaseConnection:
 ...
 def __exit__ (self, type, value, tb):
 if tb is None:
 # No exception, so commit
 self.commit()
 else:
 # Exception occurred, so rollback.
 self.rollback()
 # return False
</pre></div>
</div>
</div>
<div class="section" id="the-contextlib-module">
<h3>The contextlib module<a class="headerlink" href="#the-contextlib-module" title="Permalink to this headline">¶</a></h3>
The new <a class="reference internal" href="../library/contextlib.html#module-contextlib" title="contextlib: Utilities for with-statement contexts."><tt class="xref py py-mod docutils literal">contextlib</tt></a> module provides some functions and a decorator that
are useful for writing objects for use with the &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement.
The decorator is called <tt class="xref py py-func docutils literal">contextmanager()</tt>, and lets you write a single
generator function instead of defining a new class. The generator should yield
exactly one value. The code up to the <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> will be executed as the
<a class="reference internal" href="../reference/datamodel.html#object.__enter__" title="object.__enter__"><tt class="xref py py-meth docutils literal">__enter__()</tt></a> method, and the value yielded will be the method&#8217;s return
value that will get bound to the variable in the &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement&#8217;s
<a class="reference internal" href="../reference/compound_stmts.html#as"><tt class="xref std std-keyword docutils literal">as</tt></a> clause, if any. The code after the <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> will be
executed in the <a class="reference internal" href="../reference/datamodel.html#object.__exit__" title="object.__exit__"><tt class="xref py py-meth docutils literal">__exit__()</tt></a> method. Any exception raised in the block will
be raised by the <a class="reference internal" href="../reference/simple_stmts.html#yield"><tt class="xref std std-keyword docutils literal">yield</tt></a> statement.
Our database example from the previous section could be written using this
decorator as:
<div class="highlight-python"><div class="highlight"><pre>from contextlib import contextmanager

@contextmanager
def db_transaction (connection):
 cursor = connection.cursor()
 try:
 yield cursor
 except:
 connection.rollback()
 raise
 else:
 connection.commit()

db = DatabaseConnection()
with db_transaction(db) as cursor:
 ...
</pre></div>
</div>
The <a class="reference internal" href="../library/contextlib.html#module-contextlib" title="contextlib: Utilities for with-statement contexts."><tt class="xref py py-mod docutils literal">contextlib</tt></a> module also has a <tt class="xref py py-func docutils literal">nested(mgr1, mgr2, ...)()</tt> function
that combines a number of context managers so you don&#8217;t need to write nested
&#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statements. In this example, the single &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216;
statement both starts a database transaction and acquires a thread lock:
<div class="highlight-python"><div class="highlight"><pre>lock = threading.Lock()
with nested (db_transaction(db), lock) as (cursor, locked):
 ...
</pre></div>
</div>
Finally, the <tt class="xref py py-func docutils literal">closing(object)()</tt> function returns object so that it can be
bound to a variable, and calls <tt class="docutils literal">object.close</tt> at the end of the block.
<div class="highlight-python"><div class="highlight"><pre>import urllib, sys
from contextlib import closing

with closing(urllib.urlopen(&#39;http://www.yahoo.com&#39;)) as f:
 for line in f:
 sys.stdout.write(line)
</pre></div>
</div>
<div class="admonition-see-also admonition seealso">
See also
<dl class="docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0343">PEP 343</a> - The &#8220;with&#8221; statement</dt>
<dd>PEP written by Guido van Rossum and Nick Coghlan; implemented by Mike Bland,
Guido van Rossum, and Neal Norwitz. The PEP shows the code generated for a
&#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement, which can be helpful in learning how the statement
works.</dd>
</dl>
The documentation for the <a class="reference internal" href="../library/contextlib.html#module-contextlib" title="contextlib: Utilities for with-statement contexts."><tt class="xref py py-mod docutils literal">contextlib</tt></a> module.
</div>
</div>
</div>
<div class="section" id="pep-352-exceptions-as-new-style-classes">
<h2>PEP 352: Exceptions as New-Style Classes<a class="headerlink" href="#pep-352-exceptions-as-new-style-classes" title="Permalink to this headline">¶</a></h2>
Exception classes can now be new-style classes, not just classic classes, and
the built-in <a class="reference internal" href="../library/exceptions.html#exceptions.Exception" title="exceptions.Exception"><tt class="xref py py-exc docutils literal">Exception</tt></a> class and all the standard built-in exceptions
(<a class="reference internal" href="../library/exceptions.html#exceptions.NameError" title="exceptions.NameError"><tt class="xref py py-exc docutils literal">NameError</tt></a>, <a class="reference internal" href="../library/exceptions.html#exceptions.ValueError" title="exceptions.ValueError"><tt class="xref py py-exc docutils literal">ValueError</tt></a>, etc.) are now new-style classes.
The inheritance hierarchy for exceptions has been rearranged a bit. In 2.5, the
inheritance relationships are:
<div class="highlight-python"><pre>BaseException # New in Python 2.5
|- KeyboardInterrupt
|- SystemExit
|- Exception
 |- (all other current built-in exceptions)</pre>
</div>
This rearrangement was done because people often want to catch all exceptions
that indicate program errors. <a class="reference internal" href="../library/exceptions.html#exceptions.KeyboardInterrupt" title="exceptions.KeyboardInterrupt"><tt class="xref py py-exc docutils literal">KeyboardInterrupt</tt></a> and <a class="reference internal" href="../library/exceptions.html#exceptions.SystemExit" title="exceptions.SystemExit"><tt class="xref py py-exc docutils literal">SystemExit</tt></a>
aren&#8217;t errors, though, and usually represent an explicit action such as the user
hitting Control-C or code calling <a class="reference internal" href="../library/sys.html#sys.exit" title="sys.exit"><tt class="xref py py-func docutils literal">sys.exit()</tt></a>. A bare <tt class="docutils literal">except:</tt> will
catch all exceptions, so you commonly need to list <a class="reference internal" href="../library/exceptions.html#exceptions.KeyboardInterrupt" title="exceptions.KeyboardInterrupt"><tt class="xref py py-exc docutils literal">KeyboardInterrupt</tt></a> and
<a class="reference internal" href="../library/exceptions.html#exceptions.SystemExit" title="exceptions.SystemExit"><tt class="xref py py-exc docutils literal">SystemExit</tt></a> in order to re-raise them. The usual pattern is:
<div class="highlight-python"><pre>try:
 ...
except (KeyboardInterrupt, SystemExit):
 raise
except:
 # Log error...
 # Continue running program...</pre>
</div>
In Python 2.5, you can now write <tt class="docutils literal">except Exception</tt> to achieve the same
result, catching all the exceptions that usually indicate errors but leaving
<a class="reference internal" href="../library/exceptions.html#exceptions.KeyboardInterrupt" title="exceptions.KeyboardInterrupt"><tt class="xref py py-exc docutils literal">KeyboardInterrupt</tt></a> and <a class="reference internal" href="../library/exceptions.html#exceptions.SystemExit" title="exceptions.SystemExit"><tt class="xref py py-exc docutils literal">SystemExit</tt></a> alone. As in previous versions,
a bare <tt class="docutils literal">except:</tt> still catches all exceptions.
The goal for Python 3.0 is to require any class raised as an exception to derive
from <a class="reference internal" href="../library/exceptions.html#exceptions.BaseException" title="exceptions.BaseException"><tt class="xref py py-exc docutils literal">BaseException</tt></a> or some descendant of <a class="reference internal" href="../library/exceptions.html#exceptions.BaseException" title="exceptions.BaseException"><tt class="xref py py-exc docutils literal">BaseException</tt></a>, and future
releases in the Python 2.x series may begin to enforce this constraint.
Therefore, I suggest you begin making all your exception classes derive from
<a class="reference internal" href="../library/exceptions.html#exceptions.Exception" title="exceptions.Exception"><tt class="xref py py-exc docutils literal">Exception</tt></a> now. It&#8217;s been suggested that the bare <tt class="docutils literal">except:</tt> form should
be removed in Python 3.0, but Guido van Rossum hasn&#8217;t decided whether to do this
or not.
Raising of strings as exceptions, as in the statement <tt class="docutils literal">raise &quot;Error
occurred&quot;</tt>, is deprecated in Python 2.5 and will trigger a warning. The aim is
to be able to remove the string-exception feature in a few releases.
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0352">PEP 352</a> - Required Superclass for Exceptions</dt>
<dd>PEP written by Brett Cannon and Guido van Rossum; implemented by Brett Cannon.</dd>
</dl>
</div>
</div>
<div class="section" id="pep-353-using-ssize-t-as-the-index-type">
<h2>PEP 353: Using ssize_t as the index type<a class="headerlink" href="#pep-353-using-ssize-t-as-the-index-type" title="Permalink to this headline">¶</a></h2>
A wide-ranging change to Python&#8217;s C API, using a new <tt class="xref c c-type docutils literal">Py_ssize_t</tt> type
definition instead of <tt class="xref c c-type docutils literal">int</tt>, will permit the interpreter to handle more
data on 64-bit platforms. This change doesn&#8217;t affect Python&#8217;s capacity on 32-bit
platforms.
Various pieces of the Python interpreter used C&#8217;s <tt class="xref c c-type docutils literal">int</tt> type to store
sizes or counts; for example, the number of items in a list or tuple were stored
in an <tt class="xref c c-type docutils literal">int</tt>. The C compilers for most 64-bit platforms still define
<tt class="xref c c-type docutils literal">int</tt> as a 32-bit type, so that meant that lists could only hold up to
<tt class="docutils literal">2**31 - 1</tt> = 2147483647 items. (There are actually a few different
programming models that 64-bit C compilers can use &#8211; see
<a class="reference external" href="http://www.unix.org/version2/whatsnew/lp64_wp.html">http://www.unix.org/version2/whatsnew/lp64_wp.html</a> for a discussion &#8211; but the
most commonly available model leaves <tt class="xref c c-type docutils literal">int</tt> as 32 bits.)
A limit of 2147483647 items doesn&#8217;t really matter on a 32-bit platform because
you&#8217;ll run out of memory before hitting the length limit. Each list item
requires space for a pointer, which is 4 bytes, plus space for a
<a class="reference internal" href="../c-api/structures.html#PyObject" title="PyObject"><tt class="xref c c-type docutils literal">PyObject</tt></a> representing the item. 2147483647*4 is already more bytes
than a 32-bit address space can contain.
It&#8217;s possible to address that much memory on a 64-bit platform, however. The
pointers for a list that size would only require 16 GiB of space, so it&#8217;s not
unreasonable that Python programmers might construct lists that large.
Therefore, the Python interpreter had to be changed to use some type other than
<tt class="xref c c-type docutils literal">int</tt>, and this will be a 64-bit type on 64-bit platforms. The change
will cause incompatibilities on 64-bit machines, so it was deemed worth making
the transition now, while the number of 64-bit users is still relatively small.
(In 5 or 10 years, we may all be on 64-bit machines, and the transition would
be more painful then.)
This change most strongly affects authors of C extension modules. Python
strings and container types such as lists and tuples now use
<tt class="xref c c-type docutils literal">Py_ssize_t</tt> to store their size. Functions such as
<a class="reference internal" href="../c-api/list.html#PyList_Size" title="PyList_Size"><tt class="xref c c-func docutils literal">PyList_Size()</tt></a> now return <tt class="xref c c-type docutils literal">Py_ssize_t</tt>. Code in extension modules
may therefore need to have some variables changed to <tt class="xref c c-type docutils literal">Py_ssize_t</tt>.
The <a class="reference internal" href="../c-api/arg.html#PyArg_ParseTuple" title="PyArg_ParseTuple"><tt class="xref c c-func docutils literal">PyArg_ParseTuple()</tt></a> and <a class="reference internal" href="../c-api/arg.html#Py_BuildValue" title="Py_BuildValue"><tt class="xref c c-func docutils literal">Py_BuildValue()</tt></a> functions have a new
conversion code, <tt class="docutils literal">n</tt>, for <tt class="xref c c-type docutils literal">Py_ssize_t</tt>. <a class="reference internal" href="../c-api/arg.html#PyArg_ParseTuple" title="PyArg_ParseTuple"><tt class="xref c c-func docutils literal">PyArg_ParseTuple()</tt></a>&#8216;s
<tt class="docutils literal">s#</tt> and <tt class="docutils literal">t#</tt> still output <tt class="xref c c-type docutils literal">int</tt> by default, but you can define the
macro <tt class="xref c c-macro docutils literal">PY_SSIZE_T_CLEAN</tt> before including <tt class="file docutils literal">Python.h</tt> to make
them return <tt class="xref c c-type docutils literal">Py_ssize_t</tt>.
<a class="pep reference external" href="http://www.python.org/dev/peps/pep-0353">PEP 353</a> has a section on conversion guidelines that extension authors should
read to learn about supporting 64-bit platforms.
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0353">PEP 353</a> - Using ssize_t as the index type</dt>
<dd>PEP written and implemented by Martin von Löwis.</dd>
</dl>
</div>
</div>
<div class="section" id="pep-357-the-index-method">
<h2>PEP 357: The &#8216;__index__&#8217; method<a class="headerlink" href="#pep-357-the-index-method" title="Permalink to this headline">¶</a></h2>
The NumPy developers had a problem that could only be solved by adding a new
special method, <a class="reference internal" href="../reference/datamodel.html#object.__index__" title="object.__index__"><tt class="xref py py-meth docutils literal">__index__()</tt></a>. When using slice notation, as in
<tt class="docutils literal">[start:stop:step]</tt>, the values of the start, stop, and step indexes
must all be either integers or long integers. NumPy defines a variety of
specialized integer types corresponding to unsigned and signed integers of 8,
16, 32, and 64 bits, but there was no way to signal that these types could be
used as slice indexes.
Slicing can&#8217;t just use the existing <a class="reference internal" href="../reference/datamodel.html#object.__int__" title="object.__int__"><tt class="xref py py-meth docutils literal">__int__()</tt></a> method because that method
is also used to implement coercion to integers. If slicing used
<a class="reference internal" href="../reference/datamodel.html#object.__int__" title="object.__int__"><tt class="xref py py-meth docutils literal">__int__()</tt></a>, floating-point numbers would also become legal slice indexes
and that&#8217;s clearly an undesirable behaviour.
Instead, a new special method called <a class="reference internal" href="../reference/datamodel.html#object.__index__" title="object.__index__"><tt class="xref py py-meth docutils literal">__index__()</tt></a> was added. It takes no
arguments and returns an integer giving the slice index to use. For example:
<div class="highlight-python"><div class="highlight"><pre>class C:
 def __index__ (self):
 return self.value
</pre></div>
</div>
The return value must be either a Python integer or long integer. The
interpreter will check that the type returned is correct, and raises a
<a class="reference internal" href="../library/exceptions.html#exceptions.TypeError" title="exceptions.TypeError"><tt class="xref py py-exc docutils literal">TypeError</tt></a> if this requirement isn&#8217;t met.
A corresponding <tt class="xref py py-attr docutils literal">nb_index</tt> slot was added to the C-level
<a class="reference internal" href="../c-api/typeobj.html#PyNumberMethods" title="PyNumberMethods"><tt class="xref c c-type docutils literal">PyNumberMethods</tt></a> structure to let C extensions implement this protocol.
<tt class="xref c c-func docutils literal">PyNumber_Index(obj)()</tt> can be used in extension code to call the
<a class="reference internal" href="../reference/datamodel.html#object.__index__" title="object.__index__"><tt class="xref py py-meth docutils literal">__index__()</tt></a> function and retrieve its result.
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0357">PEP 357</a> - Allowing Any Object to be Used for Slicing</dt>
<dd>PEP written and implemented by Travis Oliphant.</dd>
</dl>
</div>
</div>
<div class="section" id="other-language-changes">
<h2>Other Language Changes<a class="headerlink" href="#other-language-changes" title="Permalink to this headline">¶</a></h2>
Here are all of the changes that Python 2.5 makes to the core Python language.
<ul>
<li>The <a class="reference internal" href="../library/stdtypes.html#dict" title="dict"><tt class="xref py py-class docutils literal">dict</tt></a> type has a new hook for letting subclasses provide a default
value when a key isn&#8217;t contained in the dictionary. When a key isn&#8217;t found, the
dictionary&#8217;s <tt class="xref py py-meth docutils literal">__missing__(key)()</tt> method will be called. This hook is used
to implement the new <tt class="xref py py-class docutils literal">defaultdict</tt> class in the <a class="reference internal" href="../library/collections.html#module-collections" title="collections: High-performance datatypes"><tt class="xref py py-mod docutils literal">collections</tt></a>
module. The following example defines a dictionary that returns zero for any
missing key:
<div class="highlight-python"><div class="highlight"><pre>class zerodict (dict):
 def __missing__ (self, key):
 return 0

d = zerodict({1:1, 2:2})
print d[1], d[2] # Prints 1, 2
print d[3], d[4] # Prints 0, 0
</pre></div>
</div>
</li>
<li>Both 8-bit and Unicode strings have new <tt class="xref py py-meth docutils literal">partition(sep)()</tt> and
<tt class="xref py py-meth docutils literal">rpartition(sep)()</tt> methods that simplify a common use case.
The <tt class="xref py py-meth docutils literal">find(S)()</tt> method is often used to get an index which is then used to
slice the string and obtain the pieces that are before and after the separator.
<tt class="xref py py-meth docutils literal">partition(sep)()</tt> condenses this pattern into a single method call that
returns a 3-tuple containing the substring before the separator, the separator
itself, and the substring after the separator. If the separator isn&#8217;t found,
the first element of the tuple is the entire string and the other two elements
are empty. <tt class="xref py py-meth docutils literal">rpartition(sep)()</tt> also returns a 3-tuple but starts searching
from the end of the string; the <tt class="docutils literal">r</tt> stands for &#8216;reverse&#8217;.
Some examples:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; (&#39;http://www.python.org&#39;).partition(&#39;://&#39;)
(&#39;http&#39;, &#39;://&#39;, &#39;www.python.org&#39;)
&gt;&gt;&gt; (&#39;file:/usr/share/doc/index.html&#39;).partition(&#39;://&#39;)
(&#39;file:/usr/share/doc/index.html&#39;, &#39;&#39;, &#39;&#39;)
&gt;&gt;&gt; (u&#39;Subject: a quick question&#39;).partition(&#39;:&#39;)
(u&#39;Subject&#39;, u&#39;:&#39;, u&#39; a quick question&#39;)
&gt;&gt;&gt; &#39;www.python.org&#39;.rpartition(&#39;.&#39;)
(&#39;www.python&#39;, &#39;.&#39;, &#39;org&#39;)
&gt;&gt;&gt; &#39;www.python.org&#39;.rpartition(&#39;:&#39;)
(&#39;&#39;, &#39;&#39;, &#39;www.python.org&#39;)
</pre></div>
</div>
(Implemented by Fredrik Lundh following a suggestion by Raymond Hettinger.)
</li>
<li>The <tt class="xref py py-meth docutils literal">startswith()</tt> and <tt class="xref py py-meth docutils literal">endswith()</tt> methods of string types now accept
tuples of strings to check for.
<div class="highlight-python"><div class="highlight"><pre>def is_image_file (filename):
 return filename.endswith((&#39;.gif&#39;, &#39;.jpg&#39;, &#39;.tiff&#39;))
</pre></div>
</div>
(Implemented by Georg Brandl following a suggestion by Tom Lynn.)
</li>
<li>The <a class="reference internal" href="../library/functions.html#min" title="min"><tt class="xref py py-func docutils literal">min()</tt></a> and <a class="reference internal" href="../library/functions.html#max" title="max"><tt class="xref py py-func docutils literal">max()</tt></a> built-in functions gained a <tt class="docutils literal">key</tt> keyword
parameter analogous to the <tt class="docutils literal">key</tt> argument for <tt class="xref py py-meth docutils literal">sort()</tt>. This parameter
supplies a function that takes a single argument and is called for every value
in the list; <a class="reference internal" href="../library/functions.html#min" title="min"><tt class="xref py py-func docutils literal">min()</tt></a>/<a class="reference internal" href="../library/functions.html#max" title="max"><tt class="xref py py-func docutils literal">max()</tt></a> will return the element with the
smallest/largest return value from this function. For example, to find the
longest string in a list, you can do:
<div class="highlight-python"><div class="highlight"><pre>L = [&#39;medium&#39;, &#39;longest&#39;, &#39;short&#39;]
# Prints &#39;longest&#39;
print max(L, key=len)
# Prints &#39;short&#39;, because lexicographically &#39;short&#39; has the largest value
print max(L)
</pre></div>
</div>
(Contributed by Steven Bethard and Raymond Hettinger.)
</li>
<li>Two new built-in functions, <a class="reference internal" href="../library/functions.html#any" title="any"><tt class="xref py py-func docutils literal">any()</tt></a> and <a class="reference internal" href="../library/functions.html#all" title="all"><tt class="xref py py-func docutils literal">all()</tt></a>, evaluate whether an
iterator contains any true or false values. <a class="reference internal" href="../library/functions.html#any" title="any"><tt class="xref py py-func docutils literal">any()</tt></a> returns <a class="reference internal" href="../library/constants.html#True" title="True"><tt class="xref py py-const docutils literal">True</tt></a>
if any value returned by the iterator is true; otherwise it will return
<a class="reference internal" href="../library/constants.html#False" title="False"><tt class="xref py py-const docutils literal">False</tt></a>. <a class="reference internal" href="../library/functions.html#all" title="all"><tt class="xref py py-func docutils literal">all()</tt></a> returns <a class="reference internal" href="../library/constants.html#True" title="True"><tt class="xref py py-const docutils literal">True</tt></a> only if all of the values
returned by the iterator evaluate as true. (Suggested by Guido van Rossum, and
implemented by Raymond Hettinger.)
</li>
<li>The result of a class&#8217;s <a class="reference internal" href="../reference/datamodel.html#object.__hash__" title="object.__hash__"><tt class="xref py py-meth docutils literal">__hash__()</tt></a> method can now be either a long
integer or a regular integer. If a long integer is returned, the hash of that
value is taken. In earlier versions the hash value was required to be a
regular integer, but in 2.5 the <a class="reference internal" href="../library/functions.html#id" title="id"><tt class="xref py py-func docutils literal">id()</tt></a> built-in was changed to always
return non-negative numbers, and users often seem to use <tt class="docutils literal">id(self)</tt> in
<a class="reference internal" href="../reference/datamodel.html#object.__hash__" title="object.__hash__"><tt class="xref py py-meth docutils literal">__hash__()</tt></a> methods (though this is discouraged).
</li>
<li>ASCII is now the default encoding for modules. It&#8217;s now a syntax error if a
module contains string literals with 8-bit characters but doesn&#8217;t have an
encoding declaration. In Python 2.4 this triggered a warning, not a syntax
error. See <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0263">PEP 263</a> for how to declare a module&#8217;s encoding; for example, you
might add a line like this near the top of the source file:
<div class="highlight-python"><div class="highlight"><pre># -*- coding: latin1 -*-
</pre></div>
</div>
</li>
<li>A new warning, <tt class="xref py py-class docutils literal">UnicodeWarning</tt>, is triggered when you attempt to
compare a Unicode string and an 8-bit string that can&#8217;t be converted to Unicode
using the default ASCII encoding. The result of the comparison is false:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; chr(128) == unichr(128) # Can&#39;t convert chr(128) to Unicode
__main__:1: UnicodeWarning: Unicode equal comparison failed
 to convert both arguments to Unicode - interpreting them
 as being unequal
False
&gt;&gt;&gt; chr(127) == unichr(127) # chr(127) can be converted
True
</pre></div>
</div>
Previously this would raise a <tt class="xref py py-class docutils literal">UnicodeDecodeError</tt> exception, but in 2.5
this could result in puzzling problems when accessing a dictionary. If you
looked up <tt class="docutils literal">unichr(128)</tt> and <tt class="docutils literal">chr(128)</tt> was being used as a key, you&#8217;d get a
<tt class="xref py py-class docutils literal">UnicodeDecodeError</tt> exception. Other changes in 2.5 resulted in this
exception being raised instead of suppressed by the code in <tt class="file docutils literal">dictobject.c</tt>
that implements dictionaries.
Raising an exception for such a comparison is strictly correct, but the change
might have broken code, so instead <tt class="xref py py-class docutils literal">UnicodeWarning</tt> was introduced.
(Implemented by Marc-André Lemburg.)
</li>
<li>One error that Python programmers sometimes make is forgetting to include an
<tt class="file docutils literal">__init__.py</tt> module in a package directory. Debugging this mistake can be
confusing, and usually requires running Python with the <a class="reference internal" href="../using/cmdline.html#cmdoption-v">-v</a> switch to
log all the paths searched. In Python 2.5, a new <a class="reference internal" href="../library/exceptions.html#exceptions.ImportWarning" title="exceptions.ImportWarning"><tt class="xref py py-exc docutils literal">ImportWarning</tt></a> warning is
triggered when an import would have picked up a directory as a package but no
<tt class="file docutils literal">__init__.py</tt> was found. This warning is silently ignored by default;
provide the -Wd option when running the Python executable to display
the warning message. (Implemented by Thomas Wouters.)
</li>
<li>The list of base classes in a class definition can now be empty. As an
example, this is now legal:
<div class="highlight-python"><div class="highlight"><pre>class C():
 pass
</pre></div>
</div>
(Implemented by Brett Cannon.)
</li>
</ul>
<div class="section" id="interactive-interpreter-changes">
<h3>Interactive Interpreter Changes<a class="headerlink" href="#interactive-interpreter-changes" title="Permalink to this headline">¶</a></h3>
In the interactive interpreter, <tt class="docutils literal">quit</tt> and <tt class="docutils literal">exit</tt> have long been strings so
that new users get a somewhat helpful message when they try to quit:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; quit
&#39;Use Ctrl-D (i.e. EOF) to exit.&#39;
</pre></div>
</div>
In Python 2.5, <tt class="docutils literal">quit</tt> and <tt class="docutils literal">exit</tt> are now objects that still produce string
representations of themselves, but are also callable. Newbies who try <tt class="docutils literal">quit()</tt>
or <tt class="docutils literal">exit()</tt> will now exit the interpreter as they expect. (Implemented by
Georg Brandl.)
The Python executable now accepts the standard long options <a class="reference internal" href="../using/cmdline.html#cmdoption--help">--help</a>
and <a class="reference internal" href="../using/cmdline.html#cmdoption--version">--version</a>; on Windows, it also accepts the /? option
for displaying a help message. (Implemented by Georg Brandl.)
</div>
<div class="section" id="optimizations">
<h3>Optimizations<a class="headerlink" href="#optimizations" title="Permalink to this headline">¶</a></h3>
Several of the optimizations were developed at the NeedForSpeed sprint, an event
held in Reykjavik, Iceland, from May 21&#8211;28 2006. The sprint focused on speed
enhancements to the CPython implementation and was funded by EWT LLC with local
support from CCP Games. Those optimizations added at this sprint are specially
marked in the following list.
<ul class="simple">
<li>When they were introduced in Python 2.4, the built-in <a class="reference internal" href="../library/stdtypes.html#set" title="set"><tt class="xref py py-class docutils literal">set</tt></a> and
<a class="reference internal" href="../library/stdtypes.html#frozenset" title="frozenset"><tt class="xref py py-class docutils literal">frozenset</tt></a> types were built on top of Python&#8217;s dictionary type. In 2.5
the internal data structure has been customized for implementing sets, and as a
result sets will use a third less memory and are somewhat faster. (Implemented
by Raymond Hettinger.)</li>
<li>The speed of some Unicode operations, such as finding substrings, string
splitting, and character map encoding and decoding, has been improved.
(Substring search and splitting improvements were added by Fredrik Lundh and
Andrew Dalke at the NeedForSpeed sprint. Character maps were improved by Walter
Dörwald and Martin von Löwis.)</li>
<li>The <tt class="xref py py-func docutils literal">long(str, base)()</tt> function is now faster on long digit strings
because fewer intermediate results are calculated. The peak is for strings of
around 800&#8211;1000 digits where the function is 6 times faster. (Contributed by
Alan McIntyre and committed at the NeedForSpeed sprint.)</li>
<li>It&#8217;s now illegal to mix iterating over a file with <tt class="docutils literal">for line in file</tt> and
calling the file object&#8217;s <tt class="xref py py-meth docutils literal">read()</tt>/<a class="reference internal" href="../library/readline.html#module-readline" title="readline: GNU readline support for Python. (Unix)"><tt class="xref py py-meth docutils literal">readline()</tt></a>/<tt class="xref py py-meth docutils literal">readlines()</tt>
methods. Iteration uses an internal buffer and the <tt class="xref py py-meth docutils literal">read*()</tt> methods
don&#8217;t use that buffer. Instead they would return the data following the
buffer, causing the data to appear out of order. Mixing iteration and these
methods will now trigger a <a class="reference internal" href="../library/exceptions.html#exceptions.ValueError" title="exceptions.ValueError"><tt class="xref py py-exc docutils literal">ValueError</tt></a> from the <tt class="xref py py-meth docutils literal">read*()</tt> method.
(Implemented by Thomas Wouters.)</li>
<li>The <a class="reference internal" href="../library/struct.html#module-struct" title="struct: Interpret strings as packed binary data."><tt class="xref py py-mod docutils literal">struct</tt></a> module now compiles structure format strings into an
internal representation and caches this representation, yielding a 20% speedup.
(Contributed by Bob Ippolito at the NeedForSpeed sprint.)</li>
<li>The <a class="reference internal" href="../library/re.html#module-re" title="re: Regular expression operations."><tt class="xref py py-mod docutils literal">re</tt></a> module got a 1 or 2% speedup by switching to Python&#8217;s allocator
functions instead of the system&#8217;s <tt class="xref c c-func docutils literal">malloc()</tt> and <tt class="xref c c-func docutils literal">free()</tt>.
(Contributed by Jack Diederich at the NeedForSpeed sprint.)</li>
<li>The code generator&#8217;s peephole optimizer now performs simple constant folding
in expressions. If you write something like <tt class="docutils literal">a = 2+3</tt>, the code generator
will do the arithmetic and produce code corresponding to <tt class="docutils literal">a = 5</tt>. (Proposed
and implemented by Raymond Hettinger.)</li>
<li>Function calls are now faster because code objects now keep the most recently
finished frame (a &#8220;zombie frame&#8221;) in an internal field of the code object,
reusing it the next time the code object is invoked. (Original patch by Michael
Hudson, modified by Armin Rigo and Richard Jones; committed at the NeedForSpeed
sprint.) Frame objects are also slightly smaller, which may improve cache
locality and reduce memory usage a bit. (Contributed by Neal Norwitz.)</li>
<li>Python&#8217;s built-in exceptions are now new-style classes, a change that speeds
up instantiation considerably. Exception handling in Python 2.5 is therefore
about 30% faster than in 2.4. (Contributed by Richard Jones, Georg Brandl and
Sean Reifschneider at the NeedForSpeed sprint.)</li>
<li>Importing now caches the paths tried, recording whether they exist or not so
that the interpreter makes fewer <tt class="xref c c-func docutils literal">open()</tt> and <tt class="xref c c-func docutils literal">stat()</tt> calls on
startup. (Contributed by Martin von Löwis and Georg Brandl.)</li>
</ul>
</div>
</div>
<div class="section" id="new-improved-and-removed-modules">
<h2>New, Improved, and Removed Modules<a class="headerlink" href="#new-improved-and-removed-modules" title="Permalink to this headline">¶</a></h2>
The standard library received many enhancements and bug fixes in Python 2.5.
Here&#8217;s a partial list of the most notable changes, sorted alphabetically by
module name. Consult the <tt class="file docutils literal">Misc/NEWS</tt> file in the source tree for a more
complete list of changes, or look through the SVN logs for all the details.
<ul>
<li>The <a class="reference internal" href="../library/audioop.html#module-audioop" title="audioop: Manipulate raw audio data."><tt class="xref py py-mod docutils literal">audioop</tt></a> module now supports the a-LAW encoding, and the code for
u-LAW encoding has been improved. (Contributed by Lars Immisch.)
</li>
<li>The <a class="reference internal" href="../library/codecs.html#module-codecs" title="codecs: Encode and decode data and streams."><tt class="xref py py-mod docutils literal">codecs</tt></a> module gained support for incremental codecs. The
<tt class="xref py py-func docutils literal">codec.lookup()</tt> function now returns a <tt class="xref py py-class docutils literal">CodecInfo</tt> instance instead
of a tuple. <tt class="xref py py-class docutils literal">CodecInfo</tt> instances behave like a 4-tuple to preserve
backward compatibility but also have the attributes <tt class="xref py py-attr docutils literal">encode</tt>,
<tt class="xref py py-attr docutils literal">decode</tt>, <tt class="xref py py-attr docutils literal">incrementalencoder</tt>, <tt class="xref py py-attr docutils literal">incrementaldecoder</tt>,
<tt class="xref py py-attr docutils literal">streamwriter</tt>, and <tt class="xref py py-attr docutils literal">streamreader</tt>. Incremental codecs can receive
input and produce output in multiple chunks; the output is the same as if the
entire input was fed to the non-incremental codec. See the <a class="reference internal" href="../library/codecs.html#module-codecs" title="codecs: Encode and decode data and streams."><tt class="xref py py-mod docutils literal">codecs</tt></a> module
documentation for details. (Designed and implemented by Walter Dörwald.)
</li>
<li>The <a class="reference internal" href="../library/collections.html#module-collections" title="collections: High-performance datatypes"><tt class="xref py py-mod docutils literal">collections</tt></a> module gained a new type, <tt class="xref py py-class docutils literal">defaultdict</tt>, that
subclasses the standard <a class="reference internal" href="../library/stdtypes.html#dict" title="dict"><tt class="xref py py-class docutils literal">dict</tt></a> type. The new type mostly behaves like a
dictionary but constructs a default value when a key isn&#8217;t present,
automatically adding it to the dictionary for the requested key value.
The first argument to <tt class="xref py py-class docutils literal">defaultdict</tt>&#8216;s constructor is a factory function
that gets called whenever a key is requested but not found. This factory
function receives no arguments, so you can use built-in type constructors such
as <a class="reference internal" href="../library/functions.html#list" title="list"><tt class="xref py py-func docutils literal">list()</tt></a> or <a class="reference internal" href="../library/functions.html#int" title="int"><tt class="xref py py-func docutils literal">int()</tt></a>. For example, you can make an index of words
based on their initial letter like this:
<div class="highlight-python"><div class="highlight"><pre>words = &quot;&quot;&quot;Nel mezzo del cammin di nostra vita
mi ritrovai per una selva oscura
che la diritta via era smarrita&quot;&quot;&quot;.lower().split()

index = defaultdict(list)

for w in words:
 init_letter = w[0]
 index[init_letter].append(w)
</pre></div>
</div>
Printing <tt class="docutils literal">index</tt> results in the following output:
<div class="highlight-python"><pre>defaultdict(&lt;type 'list'&gt;, {'c': ['cammin', 'che'], 'e': ['era'],
 'd': ['del', 'di', 'diritta'], 'm': ['mezzo', 'mi'],
 'l': ['la'], 'o': ['oscura'], 'n': ['nel', 'nostra'],
 'p': ['per'], 's': ['selva', 'smarrita'],
 'r': ['ritrovai'], 'u': ['una'], 'v': ['vita', 'via']}</pre>
</div>
(Contributed by Guido van Rossum.)
</li>
<li>The <tt class="xref py py-class docutils literal">deque</tt> double-ended queue type supplied by the <a class="reference internal" href="../library/collections.html#module-collections" title="collections: High-performance datatypes"><tt class="xref py py-mod docutils literal">collections</tt></a>
module now has a <tt class="xref py py-meth docutils literal">remove(value)()</tt> method that removes the first occurrence
of value in the queue, raising <a class="reference internal" href="../library/exceptions.html#exceptions.ValueError" title="exceptions.ValueError"><tt class="xref py py-exc docutils literal">ValueError</tt></a> if the value isn&#8217;t found.
(Contributed by Raymond Hettinger.)
</li>
<li>New module: The <a class="reference internal" href="../library/contextlib.html#module-contextlib" title="contextlib: Utilities for with-statement contexts."><tt class="xref py py-mod docutils literal">contextlib</tt></a> module contains helper functions for use
with the new &#8216;<a class="reference internal" href="../reference/compound_stmts.html#with"><tt class="xref std std-keyword docutils literal">with</tt></a>&#8216; statement. See section <a class="reference internal" href="#contextlibmod">The contextlib module</a>
for more about this module.
</li>
<li>New module: The <a class="reference internal" href="../library/profile.html#module-cProfile" title="cProfile"><tt class="xref py py-mod docutils literal">cProfile</tt></a> module is a C implementation of the existing
<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> module that has much lower overhead. The module&#8217;s interface is
the same as <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>: you run <tt class="docutils literal">cProfile.run('main()')</tt> to profile a
function, can save profile data to a file, etc. It&#8217;s not yet known if the
Hotshot profiler, which is also written in C but doesn&#8217;t match the
<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> module&#8217;s interface, will continue to be maintained in future
versions of Python. (Contributed by Armin Rigo.)
Also, the <a class="reference internal" href="../library/profile.html#module-pstats" title="pstats: Statistics object for use with the profiler."><tt class="xref py py-mod docutils literal">pstats</tt></a> module for analyzing the data measured by the profiler
now supports directing the output to any file object by supplying a stream
argument to the <tt class="xref py py-class docutils literal">Stats</tt> constructor. (Contributed by Skip Montanaro.)
</li>
<li>The <a class="reference internal" href="../library/csv.html#module-csv" title="csv: Write and read tabular data to and from delimited files."><tt class="xref py py-mod docutils literal">csv</tt></a> module, which parses files in comma-separated value format,
received several enhancements and a number of bugfixes. You can now set the
maximum size in bytes of a field by calling the
<tt class="xref py py-meth docutils literal">csv.field_size_limit(new_limit)()</tt> function; omitting the new_limit
argument will return the currently-set limit. The <tt class="xref py py-class docutils literal">reader</tt> class now has
a <tt class="xref py py-attr docutils literal">line_num</tt> attribute that counts the number of physical lines read from
the source; records can span multiple physical lines, so <tt class="xref py py-attr docutils literal">line_num</tt> is not
the same as the number of records read.
The CSV parser is now stricter about multi-line quoted fields. Previously, if a
line ended within a quoted field without a terminating newline character, a
newline would be inserted into the returned field. This behavior caused problems
when reading files that contained carriage return characters within fields, so
the code was changed to return the field without inserting newlines. As a
consequence, if newlines embedded within fields are important, the input should
be split into lines in a manner that preserves the newline characters.
(Contributed by Skip Montanaro and Andrew McNamara.)
</li>
<li>The <a class="reference internal" href="../library/datetime.html#module-datetime" title="datetime: Basic date and time types."><tt class="xref py py-class docutils literal">datetime</tt></a> class in the <a class="reference internal" href="../library/datetime.html#module-datetime" title="datetime: Basic date and time types."><tt class="xref py py-mod docutils literal">datetime</tt></a> module now has a
<tt class="xref py py-meth docutils literal">strptime(string, format)()</tt> method for parsing date strings, contributed
by Josh Spoerri. It uses the same format characters as <a class="reference internal" href="../library/time.html#time.strptime" title="time.strptime"><tt class="xref py py-func docutils literal">time.strptime()</tt></a> and
<a class="reference internal" href="../library/time.html#time.strftime" title="time.strftime"><tt class="xref py py-func docutils literal">time.strftime()</tt></a>:
<div class="highlight-python"><div class="highlight"><pre>from datetime import datetime

ts = datetime.strptime(&#39;10:13:15 2006-03-07&#39;,
 &#39;%H:%M:%S %Y-%m-%d&#39;)
</pre></div>
</div>
</li>
<li>The <tt class="xref py py-meth docutils literal">SequenceMatcher.get_matching_blocks()</tt> method in the <a class="reference internal" href="../library/difflib.html#module-difflib" title="difflib: Helpers for computing differences between objects."><tt class="xref py py-mod docutils literal">difflib</tt></a>
module now guarantees to return a minimal list of blocks describing matching
subsequences. Previously, the algorithm would occasionally break a block of
matching elements into two list entries. (Enhancement by Tim Peters.)
</li>
<li>The <a class="reference internal" href="../library/doctest.html#module-doctest" title="doctest: Test pieces of code within docstrings."><tt class="xref py py-mod docutils literal">doctest</tt></a> module gained a <tt class="docutils literal">SKIP</tt> option that keeps an example from
being executed at all. This is intended for code snippets that are usage
examples intended for the reader and aren&#8217;t actually test cases.
An encoding parameter was added to the <tt class="xref py py-func docutils literal">testfile()</tt> function and the
<tt class="xref py py-class docutils literal">DocFileSuite</tt> class to specify the file&#8217;s encoding. This makes it
easier to use non-ASCII characters in tests contained within a docstring.
(Contributed by Bjorn Tillenius.)
</li>
<li>The <a class="reference internal" href="../library/email.html#module-email" title="email: Package supporting the parsing, manipulating, and generating email messages, including MIME documents."><tt class="xref py py-mod docutils literal">email</tt></a> package has been updated to version 4.0. (Contributed by
Barry Warsaw.)
</li>
<li id="index-18">The <a class="reference internal" href="../library/fileinput.html#module-fileinput" title="fileinput: Loop over standard input or a list of files."><tt class="xref py py-mod docutils literal">fileinput</tt></a> module was made more flexible. Unicode filenames are now
supported, and a mode parameter that defaults to <tt class="docutils literal">&quot;r&quot;</tt> was added to the
<a class="reference internal" href="../library/functions.html#input" title="input"><tt class="xref py py-func docutils literal">input()</tt></a> function to allow opening files in binary or <a class="reference internal" href="../glossary.html#term-universal-newlines">universal
newlines</a> mode. Another new parameter, openhook, lets you use a function
other than <a class="reference internal" href="../library/functions.html#open" title="open"><tt class="xref py py-func docutils literal">open()</tt></a> to open the input files. Once you&#8217;re iterating over
the set of files, the <tt class="xref py py-class docutils literal">FileInput</tt> object&#8217;s new <tt class="xref py py-meth docutils literal">fileno()</tt> returns
the file descriptor for the currently opened file. (Contributed by Georg
Brandl.)
</li>
<li>In the <a class="reference internal" href="../library/gc.html#module-gc" title="gc: Interface to the cycle-detecting garbage collector."><tt class="xref py py-mod docutils literal">gc</tt></a> module, the new <tt class="xref py py-func docutils literal">get_count()</tt> function returns a 3-tuple
containing the current collection counts for the three GC generations. This is
accounting information for the garbage collector; when these counts reach a
specified threshold, a garbage collection sweep will be made. The existing
<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> function now takes an optional generation argument of 0, 1,
or 2 to specify which generation to collect. (Contributed by Barry Warsaw.)
</li>
<li>The <tt class="xref py py-func docutils literal">nsmallest()</tt> and <tt class="xref py py-func docutils literal">nlargest()</tt> functions in the <a class="reference internal" href="../library/heapq.html#module-heapq" title="heapq: Heap queue algorithm (a.k.a. priority queue)."><tt class="xref py py-mod docutils literal">heapq</tt></a>
module now support a <tt class="docutils literal">key</tt> keyword parameter similar to the one provided by
the <a class="reference internal" href="../library/functions.html#min" title="min"><tt class="xref py py-func docutils literal">min()</tt></a>/<a class="reference internal" href="../library/functions.html#max" title="max"><tt class="xref py py-func docutils literal">max()</tt></a> functions and the <tt class="xref py py-meth docutils literal">sort()</tt> methods. For
example:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; import heapq
&gt;&gt;&gt; L = [&quot;short&quot;, &#39;medium&#39;, &#39;longest&#39;, &#39;longer still&#39;]
&gt;&gt;&gt; heapq.nsmallest(2, L) # Return two lowest elements, lexicographically
[&#39;longer still&#39;, &#39;longest&#39;]
&gt;&gt;&gt; heapq.nsmallest(2, L, key=len) # Return two shortest elements
[&#39;short&#39;, &#39;medium&#39;]
</pre></div>
</div>
(Contributed by Raymond Hettinger.)
</li>
<li>The <a class="reference internal" href="../library/itertools.html#itertools.islice" title="itertools.islice"><tt class="xref py py-func docutils literal">itertools.islice()</tt></a> function now accepts <tt class="docutils literal">None</tt> for the start and
step arguments. This makes it more compatible with the attributes of slice
objects, so that you can now write the following:
<div class="highlight-python"><div class="highlight"><pre>s = slice(5) # Create slice object
itertools.islice(iterable, s.start, s.stop, s.step)
</pre></div>
</div>
(Contributed by Raymond Hettinger.)
</li>
<li>The <a class="reference internal" href="../library/functions.html#format" title="format"><tt class="xref py py-func docutils literal">format()</tt></a> function in the <a class="reference internal" href="../library/locale.html#module-locale" title="locale: Internationalization services."><tt class="xref py py-mod docutils literal">locale</tt></a> module has been modified and
two new functions were added, <tt class="xref py py-func docutils literal">format_string()</tt> and <tt class="xref py py-func docutils literal">currency()</tt>.
The <a class="reference internal" href="../library/functions.html#format" title="format"><tt class="xref py py-func docutils literal">format()</tt></a> function&#8217;s val parameter could previously be a string as
long as no more than one %char specifier appeared; now the parameter must be
exactly one %char specifier with no surrounding text. An optional monetary
parameter was also added which, if <tt class="docutils literal">True</tt>, will use the locale&#8217;s rules for
formatting currency in placing a separator between groups of three digits.
To format strings with multiple %char specifiers, use the new
<tt class="xref py py-func docutils literal">format_string()</tt> function that works like <a class="reference internal" href="../library/functions.html#format" title="format"><tt class="xref py py-func docutils literal">format()</tt></a> but also supports
mixing %char specifiers with arbitrary text.
A new <tt class="xref py py-func docutils literal">currency()</tt> function was also added that formats a number according
to the current locale&#8217;s settings.
(Contributed by Georg Brandl.)
</li>
<li>The <a class="reference internal" href="../library/mailbox.html#module-mailbox" title="mailbox: Manipulate mailboxes in various formats"><tt class="xref py py-mod docutils literal">mailbox</tt></a> module underwent a massive rewrite to add the capability to
modify mailboxes in addition to reading them. A new set of classes that include
<tt class="xref py py-class docutils literal">mbox</tt>, <tt class="xref py py-class docutils literal">MH</tt>, and <tt class="xref py py-class docutils literal">Maildir</tt> are used to read mailboxes, and
have an <tt class="xref py py-meth docutils literal">add(message)()</tt> method to add messages, <tt class="xref py py-meth docutils literal">remove(key)()</tt> to
remove messages, and <tt class="xref py py-meth docutils literal">lock()</tt>/<tt class="xref py py-meth docutils literal">unlock()</tt> to lock/unlock the mailbox.
The following example converts a maildir-format mailbox into an mbox-format
one:
<div class="highlight-python"><div class="highlight"><pre>import mailbox

# &#39;factory=None&#39; uses email.Message.Message as the class representing
# individual messages.
src = mailbox.Maildir(&#39;maildir&#39;, factory=None)
dest = mailbox.mbox(&#39;/tmp/mbox&#39;)

for msg in src:
 dest.add(msg)
</pre></div>
</div>
(Contributed by Gregory K. Johnson. Funding was provided by Google&#8217;s 2005
Summer of Code.)
</li>
<li>New module: the <a class="reference internal" href="../library/msilib.html#module-msilib" title="msilib: Creation of Microsoft Installer files, and CAB files. (Windows)"><tt class="xref py py-mod docutils literal">msilib</tt></a> module allows creating Microsoft Installer
<tt class="file docutils literal">.msi</tt> files and CAB files. Some support for reading the <tt class="file docutils literal">.msi</tt>
database is also included. (Contributed by Martin von Löwis.)
</li>
<li>The <a class="reference internal" href="../library/nis.html#module-nis" title="nis: Interface to Sun's NIS (Yellow Pages) library. (Unix)"><tt class="xref py py-mod docutils literal">nis</tt></a> module now supports accessing domains other than the system
default domain by supplying a domain argument to the <a class="reference internal" href="../library/nis.html#nis.match" title="nis.match"><tt class="xref py py-func docutils literal">nis.match()</tt></a> and
<a class="reference internal" href="../library/nis.html#nis.maps" title="nis.maps"><tt class="xref py py-func docutils literal">nis.maps()</tt></a> functions. (Contributed by Ben Bell.)
</li>
<li>The <a class="reference internal" href="../library/operator.html#module-operator" title="operator: Functions corresponding to the standard operators."><tt class="xref py py-mod docutils literal">operator</tt></a> module&#8217;s <tt class="xref py py-func docutils literal">itemgetter()</tt> and <tt class="xref py py-func docutils literal">attrgetter()</tt>
functions now support multiple fields. A call such as
<tt class="docutils literal">operator.attrgetter('a', 'b')</tt> will return a function that retrieves the
<tt class="xref py py-attr docutils literal">a</tt> and <tt class="xref py py-attr docutils literal">b</tt> attributes. Combining this new feature with the
<tt class="xref py py-meth docutils literal">sort()</tt> method&#8217;s <tt class="docutils literal">key</tt> parameter lets you easily sort lists using
multiple fields. (Contributed by Raymond Hettinger.)
</li>
<li>The <a class="reference internal" href="../library/optparse.html#module-optparse" title="optparse: Command-line option parsing library. (deprecated)"><tt class="xref py py-mod docutils literal">optparse</tt></a> module was updated to version 1.5.1 of the Optik library.
The <tt class="xref py py-class docutils literal">OptionParser</tt> class gained an <tt class="xref py py-attr docutils literal">epilog</tt> attribute, a string
that will be printed after the help message, and a <tt class="xref py py-meth docutils literal">destroy()</tt> method to
break reference cycles created by the object. (Contributed by Greg Ward.)
</li>
<li>The <a class="reference internal" href="../library/os.html#module-os" title="os: Miscellaneous operating system interfaces."><tt class="xref py py-mod docutils literal">os</tt></a> module underwent several changes. The <tt class="xref py py-attr docutils literal">stat_float_times</tt>
variable now defaults to true, meaning that <a class="reference internal" href="../library/os.html#os.stat" title="os.stat"><tt class="xref py py-func docutils literal">os.stat()</tt></a> will now return time
values as floats. (This doesn&#8217;t necessarily mean that <a class="reference internal" href="../library/os.html#os.stat" title="os.stat"><tt class="xref py py-func docutils literal">os.stat()</tt></a> will
return times that are precise to fractions of a second; not all systems support
such precision.)
Constants named <a class="reference internal" href="../library/os.html#os.SEEK_SET" title="os.SEEK_SET"><tt class="xref py py-attr docutils literal">os.SEEK_SET</tt></a>, <a class="reference internal" href="../library/os.html#os.SEEK_CUR" title="os.SEEK_CUR"><tt class="xref py py-attr docutils literal">os.SEEK_CUR</tt></a>, and
<a class="reference internal" href="../library/os.html#os.SEEK_END" title="os.SEEK_END"><tt class="xref py py-attr docutils literal">os.SEEK_END</tt></a> have been added; these are the parameters to the
<a class="reference internal" href="../library/os.html#os.lseek" title="os.lseek"><tt class="xref py py-func docutils literal">os.lseek()</tt></a> function. Two new constants for locking are
<a class="reference internal" href="../library/os.html#os.O_SHLOCK" title="os.O_SHLOCK"><tt class="xref py py-attr docutils literal">os.O_SHLOCK</tt></a> and <a class="reference internal" href="../library/os.html#os.O_EXLOCK" title="os.O_EXLOCK"><tt class="xref py py-attr docutils literal">os.O_EXLOCK</tt></a>.
Two new functions, <tt class="xref py py-func docutils literal">wait3()</tt> and <tt class="xref py py-func docutils literal">wait4()</tt>, were added. They&#8217;re similar
the <tt class="xref py py-func docutils literal">waitpid()</tt> function which waits for a child process to exit and returns
a tuple of the process ID and its exit status, but <tt class="xref py py-func docutils literal">wait3()</tt> and
<tt class="xref py py-func docutils literal">wait4()</tt> return additional information. <tt class="xref py py-func docutils literal">wait3()</tt> doesn&#8217;t take a
process ID as input, so it waits for any child process to exit and returns a
3-tuple of process-id, exit-status, resource-usage as returned from the
<a class="reference internal" href="../library/resource.html#resource.getrusage" title="resource.getrusage"><tt class="xref py py-func docutils literal">resource.getrusage()</tt></a> function. <tt class="xref py py-func docutils literal">wait4(pid)()</tt> does take a process ID.
(Contributed by Chad J. Schroeder.)
On FreeBSD, the <a class="reference internal" href="../library/os.html#os.stat" title="os.stat"><tt class="xref py py-func docutils literal">os.stat()</tt></a> function now returns times with nanosecond
resolution, and the returned object now has <tt class="xref py py-attr docutils literal">st_gen</tt> and
<tt class="xref py py-attr docutils literal">st_birthtime</tt>. The <tt class="xref py py-attr docutils literal">st_flags</tt> attribute is also available, if the
platform supports it. (Contributed by Antti Louko and Diego Pettenò.)
</li>
<li>The Python debugger provided by the <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">pdb</tt></a> module can now store lists of
commands to execute when a breakpoint is reached and execution stops. Once
breakpoint #1 has been created, enter <tt class="docutils literal">commands 1</tt> and enter a series of
commands to be executed, finishing the list with <tt class="docutils literal">end</tt>. The command list can
include commands that resume execution, such as <tt class="docutils literal">continue</tt> or <tt class="docutils literal">next</tt>.
(Contributed by Grégoire Dooms.)
</li>
<li>The <a class="reference internal" href="../library/pickle.html#module-pickle" title="pickle: Convert Python objects to streams of bytes and back."><tt class="xref py py-mod docutils literal">pickle</tt></a> and <a class="reference internal" href="../library/pickle.html#module-cPickle" title="cPickle: Faster version of pickle, but not subclassable."><tt class="xref py py-mod docutils literal">cPickle</tt></a> modules no longer accept a return value
of <tt class="docutils literal">None</tt> from the <a class="reference internal" href="../library/pickle.html#object.__reduce__" title="object.__reduce__"><tt class="xref py py-meth docutils literal">__reduce__()</tt></a> method; the method must return a tuple
of arguments instead. The ability to return <tt class="docutils literal">None</tt> was deprecated in Python
2.4, so this completes the removal of the feature.
</li>
<li>The <a class="reference internal" href="../library/pkgutil.html#module-pkgutil" title="pkgutil: Utilities for the import system."><tt class="xref py py-mod docutils literal">pkgutil</tt></a> module, containing various utility functions for finding
packages, was enhanced to support PEP 302&#8217;s import hooks and now also works for
packages stored in ZIP-format archives. (Contributed by Phillip J. Eby.)
</li>
<li>The pybench benchmark suite by Marc-André Lemburg is now included in the
<tt class="file docutils literal">Tools/pybench</tt> directory. The pybench suite is an improvement on the
commonly used <tt class="file docutils literal">pystone.py</tt> program because pybench provides a more
detailed measurement of the interpreter&#8217;s speed. It times particular operations
such as function calls, tuple slicing, method lookups, and numeric operations,
instead of performing many different operations and reducing the result to a
single number as <tt class="file docutils literal">pystone.py</tt> does.
</li>
<li>The <tt class="xref py py-mod docutils literal">pyexpat</tt> module now uses version 2.0 of the Expat parser.
(Contributed by Trent Mick.)
</li>
<li>The <a class="reference internal" href="../library/queue.html#module-Queue" title="Queue: A synchronized queue class."><tt class="xref py py-class docutils literal">Queue</tt></a> class provided by the <a class="reference internal" href="../library/queue.html#module-Queue" title="Queue: A synchronized queue class."><tt class="xref py py-mod docutils literal">Queue</tt></a> module gained two new
methods. <tt class="xref py py-meth docutils literal">join()</tt> blocks until all items in the queue have been retrieved
and all processing work on the items have been completed. Worker threads call
the other new method, <tt class="xref py py-meth docutils literal">task_done()</tt>, to signal that processing for an item
has been completed. (Contributed by Raymond Hettinger.)
</li>
<li>The old <tt class="xref py py-mod docutils literal">regex</tt> and <tt class="xref py py-mod docutils literal">regsub</tt> modules, which have been deprecated
ever since Python 2.0, have finally been deleted. Other deleted modules:
<tt class="xref py py-mod docutils literal">statcache</tt>, <tt class="xref py py-mod docutils literal">tzparse</tt>, <tt class="xref py py-mod docutils literal">whrandom</tt>.
</li>
<li>Also deleted: the <tt class="file docutils literal">lib-old</tt> directory, which includes ancient modules
such as <tt class="xref py py-mod docutils literal">dircmp</tt> and <tt class="xref py py-mod docutils literal">ni</tt>, was removed. <tt class="file docutils literal">lib-old</tt> wasn&#8217;t on the
default <tt class="docutils literal">sys.path</tt>, so unless your programs explicitly added the directory to
<tt class="docutils literal">sys.path</tt>, this removal shouldn&#8217;t affect your code.
</li>
<li>The <a class="reference internal" href="../library/rlcompleter.html#module-rlcompleter" title="rlcompleter: Python identifier completion, suitable for the GNU readline library."><tt class="xref py py-mod docutils literal">rlcompleter</tt></a> module is no longer dependent on importing the
<a class="reference internal" href="../library/readline.html#module-readline" title="readline: GNU readline support for Python. (Unix)"><tt class="xref py py-mod docutils literal">readline</tt></a> module and therefore now works on non-Unix platforms. (Patch
from Robert Kiendl.)
</li>
<li>The <a class="reference internal" href="../library/simplexmlrpcserver.html#module-SimpleXMLRPCServer" title="SimpleXMLRPCServer: Basic XML-RPC server implementation."><tt class="xref py py-mod docutils literal">SimpleXMLRPCServer</tt></a> and <a class="reference internal" href="../library/docxmlrpcserver.html#module-DocXMLRPCServer" title="DocXMLRPCServer: Self-documenting XML-RPC server implementation."><tt class="xref py py-mod docutils literal">DocXMLRPCServer</tt></a> classes now have a
<tt class="xref py py-attr docutils literal">rpc_paths</tt> attribute that constrains XML-RPC operations to a limited set
of URL paths; the default is to allow only <tt class="docutils literal">'/'</tt> and <tt class="docutils literal">'/RPC2'</tt>. Setting
<tt class="xref py py-attr docutils literal">rpc_paths</tt> to <tt class="docutils literal">None</tt> or an empty tuple disables this path checking.
</li>
<li>The <a class="reference internal" href="../library/socket.html#module-socket" title="socket: Low-level networking interface."><tt class="xref py py-mod docutils literal">socket</tt></a> module now supports <tt class="xref py py-const docutils literal">AF_NETLINK</tt> sockets on Linux,
thanks to a patch from Philippe Biondi. Netlink sockets are a Linux-specific
mechanism for communications between a user-space process and kernel code; an
introductory article about them is at <a class="reference external" href="http://www.linuxjournal.com/article/7356">http://www.linuxjournal.com/article/7356</a>.
In Python code, netlink addresses are represented as a tuple of 2 integers,
<tt class="docutils literal">(pid, group_mask)</tt>.
Two new methods on socket objects, <tt class="xref py py-meth docutils literal">recv_into(buffer)()</tt> and
<tt class="xref py py-meth docutils literal">recvfrom_into(buffer)()</tt>, store the received data in an object that
supports the buffer protocol instead of returning the data as a string. This
means you can put the data directly into an array or a memory-mapped file.
Socket objects also gained <tt class="xref py py-meth docutils literal">getfamily()</tt>, <tt class="xref py py-meth docutils literal">gettype()</tt>, and
<tt class="xref py py-meth docutils literal">getproto()</tt> accessor methods to retrieve the family, type, and protocol
values for the socket.
</li>
<li>New module: the <a class="reference internal" href="../library/spwd.html#module-spwd" title="spwd: The shadow password database (getspnam() and friends). (Unix)"><tt class="xref py py-mod docutils literal">spwd</tt></a> module provides functions for accessing the shadow
password database on systems that support shadow passwords.
</li>
<li>The <a class="reference internal" href="../library/struct.html#module-struct" title="struct: Interpret strings as packed binary data."><tt class="xref py py-mod docutils literal">struct</tt></a> is now faster because it compiles format strings into
<tt class="xref py py-class docutils literal">Struct</tt> objects with <tt class="xref py py-meth docutils literal">pack()</tt> and <tt class="xref py py-meth docutils literal">unpack()</tt> methods. This is
similar to how the <a class="reference internal" href="../library/re.html#module-re" title="re: Regular expression operations."><tt class="xref py py-mod docutils literal">re</tt></a> module lets you create compiled regular expression
objects. You can still use the module-level <tt class="xref py py-func docutils literal">pack()</tt> and <tt class="xref py py-func docutils literal">unpack()</tt>
functions; they&#8217;ll create <tt class="xref py py-class docutils literal">Struct</tt> objects and cache them. Or you can
use <tt class="xref py py-class docutils literal">Struct</tt> instances directly:
<div class="highlight-python"><div class="highlight"><pre>s = struct.Struct(&#39;ih3s&#39;)

data = s.pack(1972, 187, &#39;abc&#39;)
year, number, name = s.unpack(data)
</pre></div>
</div>
You can also pack and unpack data to and from buffer objects directly using the
<tt class="xref py py-meth docutils literal">pack_into(buffer, offset, v1, v2, ...)()</tt> and <tt class="xref py py-meth docutils literal">unpack_from(buffer,
offset)()</tt> methods. This lets you store data directly into an array or a memory-
mapped file.
(<tt class="xref py py-class docutils literal">Struct</tt> objects were implemented by Bob Ippolito at the NeedForSpeed
sprint. Support for buffer objects was added by Martin Blais, also at the
NeedForSpeed sprint.)
</li>
<li>The Python developers switched from CVS to Subversion during the 2.5
development process. Information about the exact build version is available as
the <tt class="docutils literal">sys.subversion</tt> variable, a 3-tuple of <tt class="docutils literal">(interpreter-name, branch-name,
revision-range)</tt>. For example, at the time of writing my copy of 2.5 was
reporting <tt class="docutils literal">('CPython', 'trunk', '45313:45315')</tt>.
This information is also available to C extensions via the
<a class="reference internal" href="../c-api/init.html#Py_GetBuildInfo" title="Py_GetBuildInfo"><tt class="xref c c-func docutils literal">Py_GetBuildInfo()</tt></a> function that returns a string of build information
like this: <tt class="docutils literal">&quot;trunk:45355:45356M, Apr 13 2006, 07:42:19&quot;</tt>. (Contributed by
Barry Warsaw.)
</li>
<li>Another new function, <a class="reference internal" href="../library/sys.html#sys._current_frames" title="sys._current_frames"><tt class="xref py py-func docutils literal">sys._current_frames()</tt></a>, returns the current stack
frames for all running threads as a dictionary mapping thread identifiers to the
topmost stack frame currently active in that thread at the time the function is
called. (Contributed by Tim Peters.)
</li>
<li>The <tt class="xref py py-class docutils literal">TarFile</tt> class in the <a class="reference internal" href="../library/tarfile.html#module-tarfile" title="tarfile: Read and write tar-format archive files."><tt class="xref py py-mod docutils literal">tarfile</tt></a> module now has an
<tt class="xref py py-meth docutils literal">extractall()</tt> method that extracts all members from the archive into the
current working directory. It&#8217;s also possible to set a different directory as
the extraction target, and to unpack only a subset of the archive&#8217;s members.
The compression used for a tarfile opened in stream mode can now be autodetected
using the mode <tt class="docutils literal">'r|*'</tt>. (Contributed by Lars Gustäbel.)
</li>
<li>The <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> module now lets you set the stack size used when new
threads are created. The <tt class="xref py py-func docutils literal">stack_size([*size*])()</tt> function returns the
currently configured stack size, and supplying the optional size parameter
sets a new value. Not all platforms support changing the stack size, but
Windows, POSIX threading, and OS/2 all do. (Contributed by Andrew MacIntyre.)
</li>
<li>The <a class="reference internal" href="../library/unicodedata.html#module-unicodedata" title="unicodedata: Access the Unicode Database."><tt class="xref py py-mod docutils literal">unicodedata</tt></a> module has been updated to use version 4.1.0 of the
Unicode character database. Version 3.2.0 is required by some specifications,
so it&#8217;s still available as <a class="reference internal" href="../library/unicodedata.html#unicodedata.ucd_3_2_0" title="unicodedata.ucd_3_2_0"><tt class="xref py py-attr docutils literal">unicodedata.ucd_3_2_0</tt></a>.
</li>
<li>New module: the <a class="reference internal" href="../library/uuid.html#module-uuid" title="uuid: UUID objects (universally unique identifiers) according to RFC 4122"><tt class="xref py py-mod docutils literal">uuid</tt></a> module generates universally unique identifiers
(UUIDs) according to <a class="rfc reference external" href="http://tools.ietf.org/html/rfc4122.html">RFC 4122</a>. The RFC defines several different UUID
versions that are generated from a starting string, from system properties, or
purely randomly. This module contains a <tt class="xref py py-class docutils literal">UUID</tt> class and functions
named <tt class="xref py py-func docutils literal">uuid1()</tt>, <tt class="xref py py-func docutils literal">uuid3()</tt>, <tt class="xref py py-func docutils literal">uuid4()</tt>, and <tt class="xref py py-func docutils literal">uuid5()</tt> to
generate different versions of UUID. (Version 2 UUIDs are not specified in
<a class="rfc reference external" href="http://tools.ietf.org/html/rfc4122.html">RFC 4122</a> and are not supported by this module.)
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; import uuid
&gt;&gt;&gt; # make a UUID based on the host ID and current time
&gt;&gt;&gt; uuid.uuid1()
UUID(&#39;a8098c1a-f86e-11da-bd1a-00112444be1e&#39;)

&gt;&gt;&gt; # make a UUID using an MD5 hash of a namespace UUID and a name
&gt;&gt;&gt; uuid.uuid3(uuid.NAMESPACE_DNS, &#39;python.org&#39;)
UUID(&#39;6fa459ea-ee8a-3ca4-894e-db77e160355e&#39;)

&gt;&gt;&gt; # make a random UUID
&gt;&gt;&gt; uuid.uuid4()
UUID(&#39;16fd2706-8baf-433b-82eb-8c7fada847da&#39;)

&gt;&gt;&gt; # make a UUID using a SHA-1 hash of a namespace UUID and a name
&gt;&gt;&gt; uuid.uuid5(uuid.NAMESPACE_DNS, &#39;python.org&#39;)
UUID(&#39;886313e1-3b8a-5372-9b90-0c9aee199e5d&#39;)
</pre></div>
</div>
(Contributed by Ka-Ping Yee.)
</li>
<li>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&#8217;s <tt class="xref py py-class docutils literal">WeakKeyDictionary</tt> and
<tt class="xref py py-class docutils literal">WeakValueDictionary</tt> types gained new methods for iterating over the
weak references contained in the dictionary. <tt class="xref py py-meth docutils literal">iterkeyrefs()</tt> and
<tt class="xref py py-meth docutils literal">keyrefs()</tt> methods were added to <tt class="xref py py-class docutils literal">WeakKeyDictionary</tt>, and
<tt class="xref py py-meth docutils literal">itervaluerefs()</tt> and <tt class="xref py py-meth docutils literal">valuerefs()</tt> were added to
<tt class="xref py py-class docutils literal">WeakValueDictionary</tt>. (Contributed by Fred L. Drake, Jr.)
</li>
<li>The <a class="reference internal" href="../library/webbrowser.html#module-webbrowser" title="webbrowser: Easy-to-use controller for Web browsers."><tt class="xref py py-mod docutils literal">webbrowser</tt></a> module received a number of enhancements. It&#8217;s now
usable as a script with <tt class="docutils literal">python -m webbrowser</tt>, taking a URL as the argument;
there are a number of switches to control the behaviour (-n for a new
browser window, <a class="reference internal" href="../using/cmdline.html#cmdoption-t">-t</a> for a new tab). New module-level functions,
<tt class="xref py py-func docutils literal">open_new()</tt> and <tt class="xref py py-func docutils literal">open_new_tab()</tt>, were added to support this. The
module&#8217;s <a class="reference internal" href="../library/functions.html#open" title="open"><tt class="xref py py-func docutils literal">open()</tt></a> function supports an additional feature, an autoraise
parameter that signals whether to raise the open window when possible. A number
of additional browsers were added to the supported list such as Firefox, Opera,
Konqueror, and elinks. (Contributed by Oleg Broytmann and Georg Brandl.)
</li>
<li>The <a class="reference internal" href="../library/xmlrpclib.html#module-xmlrpclib" title="xmlrpclib: XML-RPC client access."><tt class="xref py py-mod docutils literal">xmlrpclib</tt></a> module now supports returning <a class="reference internal" href="../library/datetime.html#module-datetime" title="datetime: Basic date and time types."><tt class="xref py py-class docutils literal">datetime</tt></a> objects
for the XML-RPC date type. Supply <tt class="docutils literal">use_datetime=True</tt> to the <tt class="xref py py-func docutils literal">loads()</tt>
function or the <tt class="xref py py-class docutils literal">Unmarshaller</tt> class to enable this feature. (Contributed
by Skip Montanaro.)
</li>
<li>The <a class="reference internal" href="../library/zipfile.html#module-zipfile" title="zipfile: Read and write ZIP-format archive files."><tt class="xref py py-mod docutils literal">zipfile</tt></a> module now supports the ZIP64 version of the format,
meaning that a .zip archive can now be larger than 4 GiB and can contain
individual files larger than 4 GiB. (Contributed by Ronald Oussoren.)
</li>
<li>The <a class="reference internal" href="../library/zlib.html#module-zlib" title="zlib: Low-level interface to compression and decompression routines compatible with gzip."><tt class="xref py py-mod docutils literal">zlib</tt></a> module&#8217;s <tt class="xref py py-class docutils literal">Compress</tt> and <tt class="xref py py-class docutils literal">Decompress</tt> objects now
support a <a class="reference internal" href="../library/copy.html#module-copy" title="copy: Shallow and deep copy operations."><tt class="xref py py-meth docutils literal">copy()</tt></a> method that makes a copy of the object&#8217;s internal state
and returns a new <tt class="xref py py-class docutils literal">Compress</tt> or <tt class="xref py py-class docutils literal">Decompress</tt> object.
(Contributed by Chris AtLee.)
</li>
</ul>
<div class="section" id="the-ctypes-package">
<h3>The ctypes package<a class="headerlink" href="#the-ctypes-package" title="Permalink to this headline">¶</a></h3>
The <a class="reference internal" href="../library/ctypes.html#module-ctypes" title="ctypes: A foreign function library for Python."><tt class="xref py py-mod docutils literal">ctypes</tt></a> package, written by Thomas Heller, has been added to the
standard library. <a class="reference internal" href="../library/ctypes.html#module-ctypes" title="ctypes: A foreign function library for Python."><tt class="xref py py-mod docutils literal">ctypes</tt></a> lets you call arbitrary functions in shared
libraries or DLLs. Long-time users may remember the <a class="reference internal" href="../library/dl.html#module-dl" title="dl: Call C functions in shared objects. (deprecated) (Unix)"><tt class="xref py py-mod docutils literal">dl</tt></a> module, which
provides functions for loading shared libraries and calling functions in them.
The <a class="reference internal" href="../library/ctypes.html#module-ctypes" title="ctypes: A foreign function library for Python."><tt class="xref py py-mod docutils literal">ctypes</tt></a> package is much fancier.
To load a shared library or DLL, you must create an instance of the
<tt class="xref py py-class docutils literal">CDLL</tt> class and provide the name or path of the shared library or DLL.
Once that&#8217;s done, you can call arbitrary functions by accessing them as
attributes of the <tt class="xref py py-class docutils literal">CDLL</tt> object.
<div class="highlight-python"><div class="highlight"><pre>import ctypes

libc = ctypes.CDLL(&#39;libc.so.6&#39;)
result = libc.printf(&quot;Line of output\n&quot;)
</pre></div>
</div>
Type constructors for the various C types are provided: <tt class="xref py py-func docutils literal">c_int()</tt>,
<tt class="xref py py-func docutils literal">c_float()</tt>, <tt class="xref py py-func docutils literal">c_double()</tt>, <tt class="xref py py-func docutils literal">c_char_p()</tt> (equivalent to <tt class="xref c c-type docutils literal">char
*</tt>), and so forth. Unlike Python&#8217;s types, the C versions are all mutable; you
can assign to their <tt class="xref py py-attr docutils literal">value</tt> attribute to change the wrapped value. Python
integers and strings will be automatically converted to the corresponding C
types, but for other types you must call the correct type constructor. (And I
mean must; getting it wrong will often result in the interpreter crashing
with a segmentation fault.)
You shouldn&#8217;t use <tt class="xref py py-func docutils literal">c_char_p()</tt> with a Python string when the C function will
be modifying the memory area, because Python strings are supposed to be
immutable; breaking this rule will cause puzzling bugs. When you need a
modifiable memory area, use <tt class="xref py py-func docutils literal">create_string_buffer()</tt>:
<div class="highlight-python"><div class="highlight"><pre>s = &quot;this is a string&quot;
buf = ctypes.create_string_buffer(s)
libc.strfry(buf)
</pre></div>
</div>
C functions are assumed to return integers, but you can set the <tt class="xref py py-attr docutils literal">restype</tt>
attribute of the function object to change this:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; libc.atof(&#39;2.71828&#39;)
-1783957616
&gt;&gt;&gt; libc.atof.restype = ctypes.c_double
&gt;&gt;&gt; libc.atof(&#39;2.71828&#39;)
2.71828
</pre></div>
</div>
<a class="reference internal" href="../library/ctypes.html#module-ctypes" title="ctypes: A foreign function library for Python."><tt class="xref py py-mod docutils literal">ctypes</tt></a> also provides a wrapper for Python&#8217;s C API as the
<tt class="docutils literal">ctypes.pythonapi</tt> object. This object does not release the global
interpreter lock before calling a function, because the lock must be held when
calling into the interpreter&#8217;s code. There&#8217;s a <tt class="xref py py-class docutils literal">py_object()</tt> type
constructor that will create a <a class="reference internal" href="../c-api/structures.html#PyObject" title="PyObject"><tt class="xref c c-type docutils literal">PyObject *</tt></a> pointer. A simple usage:
<div class="highlight-python"><div class="highlight"><pre>import ctypes

d = {}
ctypes.pythonapi.PyObject_SetItem(ctypes.py_object(d),
 ctypes.py_object(&quot;abc&quot;), ctypes.py_object(1))
# d is now {&#39;abc&#39;, 1}.
</pre></div>
</div>
Don&#8217;t forget to use <tt class="xref py py-class docutils literal">py_object()</tt>; if it&#8217;s omitted you end up with a
segmentation fault.
<a class="reference internal" href="../library/ctypes.html#module-ctypes" title="ctypes: A foreign function library for Python."><tt class="xref py py-mod docutils literal">ctypes</tt></a> has been around for a while, but people still write and
distribution hand-coded extension modules because you can&#8217;t rely on
<a class="reference internal" href="../library/ctypes.html#module-ctypes" title="ctypes: A foreign function library for Python."><tt class="xref py py-mod docutils literal">ctypes</tt></a> being present. Perhaps developers will begin to write Python
wrappers atop a library accessed through <a class="reference internal" href="../library/ctypes.html#module-ctypes" title="ctypes: A foreign function library for Python."><tt class="xref py py-mod docutils literal">ctypes</tt></a> instead of extension
modules, now that <a class="reference internal" href="../library/ctypes.html#module-ctypes" title="ctypes: A foreign function library for Python."><tt class="xref py py-mod docutils literal">ctypes</tt></a> is included with core Python.
<div class="admonition-see-also admonition seealso">
See also
<dl class="docutils">
<dt><a class="reference external" href="http://starship.python.net/crew/theller/ctypes/">http://starship.python.net/crew/theller/ctypes/</a></dt>
<dd>The ctypes web page, with a tutorial, reference, and FAQ.</dd>
</dl>
The documentation for the <a class="reference internal" href="../library/ctypes.html#module-ctypes" title="ctypes: A foreign function library for Python."><tt class="xref py py-mod docutils literal">ctypes</tt></a> module.
</div>
</div>
<div class="section" id="the-elementtree-package">
<h3>The ElementTree package<a class="headerlink" href="#the-elementtree-package" title="Permalink to this headline">¶</a></h3>
A subset of Fredrik Lundh&#8217;s ElementTree library for processing XML has been
added to the standard library as <tt class="xref py py-mod docutils literal">xml.etree</tt>. The available modules are
<tt class="xref py py-mod docutils literal">ElementTree</tt>, <tt class="xref py py-mod docutils literal">ElementPath</tt>, and <tt class="xref py py-mod docutils literal">ElementInclude</tt> from
ElementTree 1.2.6. The <tt class="xref py py-mod docutils literal">cElementTree</tt> accelerator module is also
included.
The rest of this section will provide a brief overview of using ElementTree.
Full documentation for ElementTree is available at
<a class="reference external" href="http://effbot.org/zone/element-index.htm">http://effbot.org/zone/element-index.htm</a>.
ElementTree represents an XML document as a tree of element nodes. The text
content of the document is stored as the <tt class="xref py py-attr docutils literal">text</tt> and <tt class="xref py py-attr docutils literal">tail</tt>
attributes of (This is one of the major differences between ElementTree and
the Document Object Model; in the DOM there are many different types of node,
including <tt class="xref py py-class docutils literal">TextNode</tt>.)
The most commonly used parsing function is <tt class="xref py py-func docutils literal">parse()</tt>, that takes either a
string (assumed to contain a filename) or a file-like object and returns an
<tt class="xref py py-class docutils literal">ElementTree</tt> instance:
<div class="highlight-python"><div class="highlight"><pre>from xml.etree import ElementTree as ET

tree = ET.parse(&#39;ex-1.xml&#39;)

feed = urllib.urlopen(
 &#39;http://planet.python.org/rss10.xml&#39;)
tree = ET.parse(feed)
</pre></div>
</div>
Once you have an <tt class="xref py py-class docutils literal">ElementTree</tt> instance, you can call its <tt class="xref py py-meth docutils literal">getroot()</tt>
method to get the root <tt class="xref py py-class docutils literal">Element</tt> node.
There&#8217;s also an <tt class="xref py py-func docutils literal">XML()</tt> function that takes a string literal and returns an
<tt class="xref py py-class docutils literal">Element</tt> node (not an <tt class="xref py py-class docutils literal">ElementTree</tt>). This function provides a
tidy way to incorporate XML fragments, approaching the convenience of an XML
literal:
<div class="highlight-python"><div class="highlight"><pre>svg = ET.XML(&quot;&quot;&quot;&lt;svg width=&quot;10px&quot; version=&quot;1.0&quot;&gt;
 &lt;/svg&gt;&quot;&quot;&quot;)
svg.set(&#39;height&#39;, &#39;320px&#39;)
svg.append(elem1)
</pre></div>
</div>
Each XML element supports some dictionary-like and some list-like access
methods. Dictionary-like operations are used to access attribute values, and
list-like operations are used to access child nodes.
<table border="1" class="docutils">
<colgroup>
<col width="41%" />
<col width="59%" />
</colgroup>
<thead valign="bottom">
<tr class="row-odd"><th class="head">Operation</th>
<th class="head">Result</th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even"><td><tt class="docutils literal">elem[n]</tt></td>
<td>Returns n&#8217;th child element.</td>
</tr>
<tr class="row-odd"><td><tt class="docutils literal">elem[m:n]</tt></td>
<td>Returns list of m&#8217;th through n&#8217;th child
elements.</td>
</tr>
<tr class="row-even"><td><tt class="docutils literal">len(elem)</tt></td>
<td>Returns number of child elements.</td>
</tr>
<tr class="row-odd"><td><tt class="docutils literal">list(elem)</tt></td>
<td>Returns list of child elements.</td>
</tr>
<tr class="row-even"><td><tt class="docutils literal">elem.append(elem2)</tt></td>
<td>Adds elem2 as a child.</td>
</tr>
<tr class="row-odd"><td><tt class="docutils literal">elem.insert(index, elem2)</tt></td>
<td>Inserts elem2 at the specified location.</td>
</tr>
<tr class="row-even"><td><tt class="docutils literal">del elem[n]</tt></td>
<td>Deletes n&#8217;th child element.</td>
</tr>
<tr class="row-odd"><td><tt class="docutils literal">elem.keys()</tt></td>
<td>Returns list of attribute names.</td>
</tr>
<tr class="row-even"><td><tt class="docutils literal">elem.get(name)</tt></td>
<td>Returns value of attribute name.</td>
</tr>
<tr class="row-odd"><td><tt class="docutils literal">elem.set(name, value)</tt></td>
<td>Sets new value for attribute name.</td>
</tr>
<tr class="row-even"><td><tt class="docutils literal">elem.attrib</tt></td>
<td>Retrieves the dictionary containing
attributes.</td>
</tr>
<tr class="row-odd"><td><tt class="docutils literal">del elem.attrib[name]</tt></td>
<td>Deletes attribute name.</td>
</tr>
</tbody>
</table>
Comments and processing instructions are also represented as <tt class="xref py py-class docutils literal">Element</tt>
nodes. To check if a node is a comment or processing instructions:
<div class="highlight-python"><div class="highlight"><pre>if elem.tag is ET.Comment:
 ...
elif elem.tag is ET.ProcessingInstruction:
 ...
</pre></div>
</div>
To generate XML output, you should call the <tt class="xref py py-meth docutils literal">ElementTree.write()</tt> method.
Like <tt class="xref py py-func docutils literal">parse()</tt>, it can take either a string or a file-like object:
<div class="highlight-python"><div class="highlight"><pre># Encoding is US-ASCII
tree.write(&#39;output.xml&#39;)

# Encoding is UTF-8
f = open(&#39;output.xml&#39;, &#39;w&#39;)
tree.write(f, encoding=&#39;utf-8&#39;)
</pre></div>
</div>
(Caution: the default encoding used for output is ASCII. For general XML work,
where an element&#8217;s name may contain arbitrary Unicode characters, ASCII isn&#8217;t a
very useful encoding because it will raise an exception if an element&#8217;s name
contains any characters with values greater than 127. Therefore, it&#8217;s best to
specify a different encoding such as UTF-8 that can handle any Unicode
character.)
This section is only a partial description of the ElementTree interfaces. Please
read the package&#8217;s official documentation for more details.
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="reference external" href="http://effbot.org/zone/element-index.htm">http://effbot.org/zone/element-index.htm</a></dt>
<dd>Official documentation for ElementTree.</dd>
</dl>
</div>
</div>
<div class="section" id="the-hashlib-package">
<h3>The hashlib package<a class="headerlink" href="#the-hashlib-package" title="Permalink to this headline">¶</a></h3>
A new <a class="reference internal" href="../library/hashlib.html#module-hashlib" title="hashlib: Secure hash and message digest algorithms."><tt class="xref py py-mod docutils literal">hashlib</tt></a> module, written by Gregory P. Smith, has been added to
replace the <a class="reference internal" href="../library/md5.html#module-md5" title="md5: RSA's MD5 message digest algorithm. (deprecated)"><tt class="xref py py-mod docutils literal">md5</tt></a> and <a class="reference internal" href="../library/sha.html#module-sha" title="sha: NIST's secure hash algorithm, SHA. (deprecated)"><tt class="xref py py-mod docutils literal">sha</tt></a> modules. <a class="reference internal" href="../library/hashlib.html#module-hashlib" title="hashlib: Secure hash and message digest algorithms."><tt class="xref py py-mod docutils literal">hashlib</tt></a> adds support for
additional secure hashes (SHA-224, SHA-256, SHA-384, and SHA-512). When
available, the module uses OpenSSL for fast platform optimized implementations
of algorithms.
The old <a class="reference internal" href="../library/md5.html#module-md5" title="md5: RSA's MD5 message digest algorithm. (deprecated)"><tt class="xref py py-mod docutils literal">md5</tt></a> and <a class="reference internal" href="../library/sha.html#module-sha" title="sha: NIST's secure hash algorithm, SHA. (deprecated)"><tt class="xref py py-mod docutils literal">sha</tt></a> modules still exist as wrappers around hashlib
to preserve backwards compatibility. The new module&#8217;s interface is very close
to that of the old modules, but not identical. The most significant difference
is that the constructor functions for creating new hashing objects are named
differently.
<div class="highlight-python"><div class="highlight"><pre># Old versions
h = md5.md5()
h = md5.new()

# New version
h = hashlib.md5()

# Old versions
h = sha.sha()
h = sha.new()

# New version
h = hashlib.sha1()

# Hash that weren&#39;t previously available
h = hashlib.sha224()
h = hashlib.sha256()
h = hashlib.sha384()
h = hashlib.sha512()

# Alternative form
h = hashlib.new(&#39;md5&#39;) # Provide algorithm as a string
</pre></div>
</div>
Once a hash object has been created, its methods are the same as before:
<tt class="xref py py-meth docutils literal">update(string)()</tt> hashes the specified string into the current digest
state, <tt class="xref py py-meth docutils literal">digest()</tt> and <tt class="xref py py-meth docutils literal">hexdigest()</tt> return the digest value as a binary
string or a string of hex digits, and <a class="reference internal" href="../library/copy.html#module-copy" title="copy: Shallow and deep copy operations."><tt class="xref py py-meth docutils literal">copy()</tt></a> returns a new hashing object
with the same digest state.
<div class="admonition-see-also admonition seealso">
See also
The documentation for the <a class="reference internal" href="../library/hashlib.html#module-hashlib" title="hashlib: Secure hash and message digest algorithms."><tt class="xref py py-mod docutils literal">hashlib</tt></a> module.
</div>
</div>
<div class="section" id="the-sqlite3-package">
<h3>The sqlite3 package<a class="headerlink" href="#the-sqlite3-package" title="Permalink to this headline">¶</a></h3>
The pysqlite module (<a class="reference external" href="http://www.pysqlite.org">http://www.pysqlite.org</a>), a wrapper for the SQLite embedded
database, has been added to the standard library under the package name
<a class="reference internal" href="../library/sqlite3.html#module-sqlite3" title="sqlite3: A DB-API 2.0 implementation using SQLite 3.x."><tt class="xref py py-mod docutils literal">sqlite3</tt></a>.
SQLite is a C library that provides a lightweight disk-based database that
doesn&#8217;t require a separate server process and allows accessing the database
using a nonstandard variant of the SQL query language. Some applications can use
SQLite for internal data storage. It&#8217;s also possible to prototype an
application using SQLite and then port the code to a larger database such as
PostgreSQL or Oracle.
pysqlite was written by Gerhard Häring and provides a SQL interface compliant
with the DB-API 2.0 specification described by <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0249">PEP 249</a>.
If you&#8217;re compiling the Python source yourself, note that the source tree
doesn&#8217;t include the SQLite code, only the wrapper module. You&#8217;ll need to have
the SQLite libraries and headers installed before compiling Python, and the
build process will compile the module when the necessary headers are available.
To use the module, you must first create a <tt class="xref py py-class docutils literal">Connection</tt> object that
represents the database. Here the data will be stored in the
<tt class="file docutils literal">/tmp/example</tt> file:
<div class="highlight-python"><div class="highlight"><pre>conn = sqlite3.connect(&#39;/tmp/example&#39;)
</pre></div>
</div>
You can also supply the special name <tt class="docutils literal">:memory:</tt> to create a database in RAM.
Once you have a <tt class="xref py py-class docutils literal">Connection</tt>, you can create a <tt class="xref py py-class docutils literal">Cursor</tt> object
and call its <tt class="xref py py-meth docutils literal">execute()</tt> method to perform SQL commands:
<div class="highlight-python"><div class="highlight"><pre>c = conn.cursor()

# Create table
c.execute(&#39;&#39;&#39;create table stocks
(date text, trans text, symbol text,
 qty real, price real)&#39;&#39;&#39;)

# Insert a row of data
c.execute(&quot;&quot;&quot;insert into stocks
 values (&#39;2006-01-05&#39;,&#39;BUY&#39;,&#39;RHAT&#39;,100,35.14)&quot;&quot;&quot;)
</pre></div>
</div>
Usually your SQL operations will need to use values from Python variables. You
shouldn&#8217;t assemble your query using Python&#8217;s string operations because doing so
is insecure; it makes your program vulnerable to an SQL injection attack.
Instead, use the DB-API&#8217;s parameter substitution. Put <tt class="docutils literal">?</tt> as a placeholder
wherever you want to use a value, and then provide a tuple of values as the
second argument to the cursor&#8217;s <tt class="xref py py-meth docutils literal">execute()</tt> method. (Other database modules
may use a different placeholder, such as <tt class="docutils literal">%s</tt> or <tt class="docutils literal">:1</tt>.) For example:
<div class="highlight-python"><div class="highlight"><pre># Never do this -- insecure!
symbol = &#39;IBM&#39;
c.execute(&quot;... where symbol = &#39;%s&#39;&quot; % symbol)

# Do this instead
t = (symbol,)
c.execute(&#39;select * from stocks where symbol=?&#39;, t)

# Larger example
for t in ((&#39;2006-03-28&#39;, &#39;BUY&#39;, &#39;IBM&#39;, 1000, 45.00),
 (&#39;2006-04-05&#39;, &#39;BUY&#39;, &#39;MSOFT&#39;, 1000, 72.00),
 (&#39;2006-04-06&#39;, &#39;SELL&#39;, &#39;IBM&#39;, 500, 53.00),
 ):
 c.execute(&#39;insert into stocks values (?,?,?,?,?)&#39;, t)
</pre></div>
</div>
To retrieve data after executing a SELECT statement, you can either treat the
cursor as an iterator, call the cursor&#8217;s <tt class="xref py py-meth docutils literal">fetchone()</tt> method to retrieve a
single matching row, or call <tt class="xref py py-meth docutils literal">fetchall()</tt> to get a list of the matching
rows.
This example uses the iterator form:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; c = conn.cursor()
&gt;&gt;&gt; c.execute(&#39;select * from stocks order by price&#39;)
&gt;&gt;&gt; for row in c:
... print row
...
(u&#39;2006-01-05&#39;, u&#39;BUY&#39;, u&#39;RHAT&#39;, 100, 35.140000000000001)
(u&#39;2006-03-28&#39;, u&#39;BUY&#39;, u&#39;IBM&#39;, 1000, 45.0)
(u&#39;2006-04-06&#39;, u&#39;SELL&#39;, u&#39;IBM&#39;, 500, 53.0)
(u&#39;2006-04-05&#39;, u&#39;BUY&#39;, u&#39;MSOFT&#39;, 1000, 72.0)
&gt;&gt;&gt;
</pre></div>
</div>
For more information about the SQL dialect supported by SQLite, see
<a class="reference external" href="http://www.sqlite.org">http://www.sqlite.org</a>.
<div class="admonition-see-also admonition seealso">
See also
<dl class="docutils">
<dt><a class="reference external" href="http://www.pysqlite.org">http://www.pysqlite.org</a></dt>
<dd>The pysqlite web page.</dd>
<dt><a class="reference external" href="http://www.sqlite.org">http://www.sqlite.org</a></dt>
<dd>The SQLite web page; the documentation describes the syntax and the available
data types for the supported SQL dialect.</dd>
</dl>
The documentation for the <a class="reference internal" href="../library/sqlite3.html#module-sqlite3" title="sqlite3: A DB-API 2.0 implementation using SQLite 3.x."><tt class="xref py py-mod docutils literal">sqlite3</tt></a> module.
<dl class="last docutils">
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0249">PEP 249</a> - Database API Specification 2.0</dt>
<dd>PEP written by Marc-André Lemburg.</dd>
</dl>
</div>
</div>
<div class="section" id="the-wsgiref-package">
<h3>The wsgiref package<a class="headerlink" href="#the-wsgiref-package" title="Permalink to this headline">¶</a></h3>
The Web Server Gateway Interface (WSGI) v1.0 defines a standard interface
between web servers and Python web applications and is described in <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0333">PEP 333</a>.
The <a class="reference internal" href="../library/wsgiref.html#module-wsgiref" title="wsgiref: WSGI Utilities and Reference Implementation."><tt class="xref py py-mod docutils literal">wsgiref</tt></a> package is a reference implementation of the WSGI
specification.
The package includes a basic HTTP server that will run a WSGI application; this
server is useful for debugging but isn&#8217;t intended for production use. Setting
up a server takes only a few lines of code:
<div class="highlight-python"><div class="highlight"><pre>from wsgiref import simple_server

wsgi_app = ...

host = &#39;&#39;
port = 8000
httpd = simple_server.make_server(host, port, wsgi_app)
httpd.serve_forever()
</pre></div>
</div>
<div class="admonition-see-also admonition seealso">
See also
<dl class="last docutils">
<dt><a class="reference external" href="http://www.wsgi.org">http://www.wsgi.org</a></dt>
<dd>A central web site for WSGI-related resources.</dd>
<dt><a class="pep reference external" href="http://www.python.org/dev/peps/pep-0333">PEP 333</a> - Python Web Server Gateway Interface v1.0</dt>
<dd>PEP written by Phillip J. Eby.</dd>
</dl>
</div>
</div>
</div>
<div class="section" id="build-and-c-api-changes">
<h2>Build and C API Changes<a class="headerlink" href="#build-and-c-api-changes" title="Permalink to this headline">¶</a></h2>
Changes to Python&#8217;s build process and to the C API include:
<ul>
<li>The Python source tree was converted from CVS to Subversion, in a complex
migration procedure that was supervised and flawlessly carried out by Martin von
Löwis. The procedure was developed as <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0347">PEP 347</a>.
</li>
<li>Coverity, a company that markets a source code analysis tool called Prevent,
provided the results of their examination of the Python source code. The
analysis found about 60 bugs that were quickly fixed. Many of the bugs were
refcounting problems, often occurring in error-handling code. See
<a class="reference external" href="http://scan.coverity.com">http://scan.coverity.com</a> for the statistics.
</li>
<li>The largest change to the C API came from <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0353">PEP 353</a>, which modifies the
interpreter to use a <tt class="xref c c-type docutils literal">Py_ssize_t</tt> type definition instead of
<tt class="xref c c-type docutils literal">int</tt>. See the earlier section <a class="reference internal" href="#pep-353">PEP 353: Using ssize_t as the index type</a> for a discussion of this
change.
</li>
<li>The design of the bytecode compiler has changed a great deal, no longer
generating bytecode by traversing the parse tree. Instead the parse tree is
converted to an abstract syntax tree (or AST), and it is the abstract syntax
tree that&#8217;s traversed to produce the bytecode.
It&#8217;s possible for Python code to obtain AST objects by using the
<a class="reference internal" href="../library/functions.html#compile" title="compile"><tt class="xref py py-func docutils literal">compile()</tt></a> built-in and specifying <tt class="docutils literal">_ast.PyCF_ONLY_AST</tt> as the value of
the flags parameter:
<div class="highlight-python"><div class="highlight"><pre>from _ast import PyCF_ONLY_AST
ast = compile(&quot;&quot;&quot;a=0
for i in range(10):
 a += i
&quot;&quot;&quot;, &quot;&lt;string&gt;&quot;, &#39;exec&#39;, PyCF_ONLY_AST)

assignment = ast.body[0]
for_loop = ast.body[1]
</pre></div>
</div>
No official documentation has been written for the AST code yet, but <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0339">PEP 339</a>
discusses the design. To start learning about the code, read the definition of
the various AST nodes in <tt class="file docutils literal">Parser/Python.asdl</tt>. A Python script reads this
file and generates a set of C structure definitions in
<tt class="file docutils literal">Include/Python-ast.h</tt>. The <tt class="xref c c-func docutils literal">PyParser_ASTFromString()</tt> and
<tt class="xref c c-func docutils literal">PyParser_ASTFromFile()</tt>, defined in <tt class="file docutils literal">Include/pythonrun.h</tt>, take
Python source as input and return the root of an AST representing the contents.
This AST can then be turned into a code object by <tt class="xref c c-func docutils literal">PyAST_Compile()</tt>. For
more information, read the source code, and then ask questions on python-dev.
The AST code was developed under Jeremy Hylton&#8217;s management, and implemented by
(in alphabetical order) Brett Cannon, Nick Coghlan, Grant Edwards, John
Ehresman, Kurt Kaiser, Neal Norwitz, Tim Peters, Armin Rigo, and Neil
Schemenauer, plus the participants in a number of AST sprints at conferences
such as PyCon.
</li>
<li>Evan Jones&#8217;s patch to obmalloc, first described in a talk at PyCon DC 2005,
was applied. Python 2.4 allocated small objects in 256K-sized arenas, but never
freed arenas. With this patch, Python will free arenas when they&#8217;re empty. The
net effect is that on some platforms, when you allocate many objects, Python&#8217;s
memory usage may actually drop when you delete them and the memory may be
returned to the operating system. (Implemented by Evan Jones, and reworked by
Tim Peters.)
Note that this change means extension modules must be more careful when
allocating memory. Python&#8217;s API has many different functions for allocating
memory that are grouped into families. For example, <a class="reference internal" href="../c-api/memory.html#PyMem_Malloc" title="PyMem_Malloc"><tt class="xref c c-func docutils literal">PyMem_Malloc()</tt></a>,
<a class="reference internal" href="../c-api/memory.html#PyMem_Realloc" title="PyMem_Realloc"><tt class="xref c c-func docutils literal">PyMem_Realloc()</tt></a>, and <a class="reference internal" href="../c-api/memory.html#PyMem_Free" title="PyMem_Free"><tt class="xref c c-func docutils literal">PyMem_Free()</tt></a> are one family that allocates
raw memory, while <tt class="xref c c-func docutils literal">PyObject_Malloc()</tt>, <tt class="xref c c-func docutils literal">PyObject_Realloc()</tt>, and
<tt class="xref c c-func docutils literal">PyObject_Free()</tt> are another family that&#8217;s supposed to be used for
creating Python objects.
Previously these different families all reduced to the platform&#8217;s
<tt class="xref c c-func docutils literal">malloc()</tt> and <tt class="xref c c-func docutils literal">free()</tt> functions. This meant it didn&#8217;t matter if
you got things wrong and allocated memory with the <tt class="xref c c-func docutils literal">PyMem()</tt> function but
freed it with the <a class="reference internal" href="../c-api/structures.html#PyObject" title="PyObject"><tt class="xref c c-func docutils literal">PyObject()</tt></a> function. With 2.5&#8217;s changes to obmalloc,
these families now do different things and mismatches will probably result in a
segfault. You should carefully test your C extension modules with Python 2.5.
</li>
<li>The built-in set types now have an official C API. Call <a class="reference internal" href="../c-api/set.html#PySet_New" title="PySet_New"><tt class="xref c c-func docutils literal">PySet_New()</tt></a>
and <a class="reference internal" href="../c-api/set.html#PyFrozenSet_New" title="PyFrozenSet_New"><tt class="xref c c-func docutils literal">PyFrozenSet_New()</tt></a> to create a new set, <a class="reference internal" href="../c-api/set.html#PySet_Add" title="PySet_Add"><tt class="xref c c-func docutils literal">PySet_Add()</tt></a> and
<a class="reference internal" href="../c-api/set.html#PySet_Discard" title="PySet_Discard"><tt class="xref c c-func docutils literal">PySet_Discard()</tt></a> to add and remove elements, and <a class="reference internal" href="../c-api/set.html#PySet_Contains" title="PySet_Contains"><tt class="xref c c-func docutils literal">PySet_Contains()</tt></a>
and <a class="reference internal" href="../c-api/set.html#PySet_Size" title="PySet_Size"><tt class="xref c c-func docutils literal">PySet_Size()</tt></a> to examine the set&#8217;s state. (Contributed by Raymond
Hettinger.)
</li>
<li>C code can now obtain information about the exact revision of the Python
interpreter by calling the <a class="reference internal" href="../c-api/init.html#Py_GetBuildInfo" title="Py_GetBuildInfo"><tt class="xref c c-func docutils literal">Py_GetBuildInfo()</tt></a> function that returns a
string of build information like this: <tt class="docutils literal">&quot;trunk:45355:45356M, Apr 13 2006,
07:42:19&quot;</tt>. (Contributed by Barry Warsaw.)
</li>
<li>Two new macros can be used to indicate C functions that are local to the
current file so that a faster calling convention can be used.
<tt class="xref c c-func docutils literal">Py_LOCAL(type)()</tt> declares the function as returning a value of the
specified type and uses a fast-calling qualifier.
<tt class="xref c c-func docutils literal">Py_LOCAL_INLINE(type)()</tt> does the same thing and also requests the
function be inlined. If <tt class="xref c c-func docutils literal">PY_LOCAL_AGGRESSIVE()</tt> is defined before
<tt class="file docutils literal">python.h</tt> is included, a set of more aggressive optimizations are enabled
for the module; you should benchmark the results to find out if these
optimizations actually make the code faster. (Contributed by Fredrik Lundh at
the NeedForSpeed sprint.)
</li>
<li><tt class="xref c c-func docutils literal">PyErr_NewException(name, base, dict)()</tt> can now accept a tuple of base
classes as its base argument. (Contributed by Georg Brandl.)
</li>
<li>The <a class="reference internal" href="../c-api/exceptions.html#PyErr_Warn" title="PyErr_Warn"><tt class="xref c c-func docutils literal">PyErr_Warn()</tt></a> function for issuing warnings is now deprecated in
favour of <tt class="xref c c-func docutils literal">PyErr_WarnEx(category, message, stacklevel)()</tt> which lets you
specify the number of stack frames separating this function and the caller. A
stacklevel of 1 is the function calling <a class="reference internal" href="../c-api/exceptions.html#PyErr_WarnEx" title="PyErr_WarnEx"><tt class="xref c c-func docutils literal">PyErr_WarnEx()</tt></a>, 2 is the
function above that, and so forth. (Added by Neal Norwitz.)
</li>
<li>The CPython interpreter is still written in C, but the code can now be
compiled with a C++ compiler without errors. (Implemented by Anthony Baxter,
Martin von Löwis, Skip Montanaro.)
</li>
<li>The <tt class="xref c c-func docutils literal">PyRange_New()</tt> function was removed. It was never documented, never
used in the core code, and had dangerously lax error checking. In the unlikely
case that your extensions were using it, you can replace it by something like
the following:
<div class="highlight-python"><pre>range = PyObject_CallFunction((PyObject*) &amp;PyRange_Type, "lll",
 start, stop, step);</pre>
</div>
</li>
</ul>
<div class="section" id="port-specific-changes">
<h3>Port-Specific Changes<a class="headerlink" href="#port-specific-changes" title="Permalink to this headline">¶</a></h3>
<ul class="simple">
<li>MacOS X (10.3 and higher): dynamic loading of modules now uses the
<tt class="xref c c-func docutils literal">dlopen()</tt> function instead of MacOS-specific functions.</li>
<li>MacOS X: an --enable-universalsdk switch was added to the
configure script that compiles the interpreter as a universal binary
able to run on both PowerPC and Intel processors. (Contributed by Ronald
Oussoren; <a class="reference external" href="http://bugs.python.org/issue2573">issue 2573</a>.)</li>
<li>Windows: <tt class="file docutils literal">.dll</tt> is no longer supported as a filename extension for
extension modules. <tt class="file docutils literal">.pyd</tt> is now the only filename extension that will be
searched for.</li>
</ul>
</div>
</div>
<div class="section" id="porting-to-python-2-5">
<h2>Porting to Python 2.5<a class="headerlink" href="#porting-to-python-2-5" title="Permalink to this headline">¶</a></h2>
This section lists previously described changes that may require changes to your
code:
<ul class="simple">
<li>ASCII is now the default encoding for modules. It&#8217;s now a syntax error if a
module contains string literals with 8-bit characters but doesn&#8217;t have an
encoding declaration. In Python 2.4 this triggered a warning, not a syntax
error.</li>
<li>Previously, the <tt class="xref py py-attr docutils literal">gi_frame</tt> attribute of a generator was always a frame
object. Because of the <a class="pep reference external" href="http://www.python.org/dev/peps/pep-0342">PEP 342</a> changes described in section <a class="reference internal" href="#pep-342">PEP 342: New Generator Features</a>,
it&#8217;s now possible for <tt class="xref py py-attr docutils literal">gi_frame</tt> to be <tt class="docutils literal">None</tt>.</li>
<li>A new warning, <tt class="xref py py-class docutils literal">UnicodeWarning</tt>, is triggered when you attempt to
compare a Unicode string and an 8-bit string that can&#8217;t be converted to Unicode
using the default ASCII encoding. Previously such comparisons would raise a
<tt class="xref py py-class docutils literal">UnicodeDecodeError</tt> exception.</li>
<li>Library: the <a class="reference internal" href="../library/csv.html#module-csv" title="csv: Write and read tabular data to and from delimited files."><tt class="xref py py-mod docutils literal">csv</tt></a> module is now stricter about multi-line quoted fields.
If your files contain newlines embedded within fields, the input should be split
into lines in a manner which preserves the newline characters.</li>
<li>Library: the <a class="reference internal" href="../library/locale.html#module-locale" title="locale: Internationalization services."><tt class="xref py py-mod docutils literal">locale</tt></a> module&#8217;s <a class="reference internal" href="../library/functions.html#format" title="format"><tt class="xref py py-func docutils literal">format()</tt></a> function&#8217;s would
previously accept any string as long as no more than one %char specifier
appeared. In Python 2.5, the argument must be exactly one %char specifier with
no surrounding text.</li>
<li>Library: The <a class="reference internal" href="../library/pickle.html#module-pickle" title="pickle: Convert Python objects to streams of bytes and back."><tt class="xref py py-mod docutils literal">pickle</tt></a> and <a class="reference internal" href="../library/pickle.html#module-cPickle" title="cPickle: Faster version of pickle, but not subclassable."><tt class="xref py py-mod docutils literal">cPickle</tt></a> modules no longer accept a
return value of <tt class="docutils literal">None</tt> from the <a class="reference internal" href="../library/pickle.html#object.__reduce__" title="object.__reduce__"><tt class="xref py py-meth docutils literal">__reduce__()</tt></a> method; the method must
return a tuple of arguments instead. The modules also no longer accept the
deprecated bin keyword parameter.</li>
<li>Library: The <a class="reference internal" href="../library/simplexmlrpcserver.html#module-SimpleXMLRPCServer" title="SimpleXMLRPCServer: Basic XML-RPC server implementation."><tt class="xref py py-mod docutils literal">SimpleXMLRPCServer</tt></a> and <a class="reference internal" href="../library/docxmlrpcserver.html#module-DocXMLRPCServer" title="DocXMLRPCServer: Self-documenting XML-RPC server implementation."><tt class="xref py py-mod docutils literal">DocXMLRPCServer</tt></a> classes now
have a <tt class="xref py py-attr docutils literal">rpc_paths</tt> attribute that constrains XML-RPC operations to a
limited set of URL paths; the default is to allow only <tt class="docutils literal">'/'</tt> and <tt class="docutils literal">'/RPC2'</tt>.
Setting <tt class="xref py py-attr docutils literal">rpc_paths</tt> to <tt class="docutils literal">None</tt> or an empty tuple disables this path
checking.</li>
<li>C API: Many functions now use <tt class="xref c c-type docutils literal">Py_ssize_t</tt> instead of <tt class="xref c c-type docutils literal">int</tt> to
allow processing more data on 64-bit machines. Extension code may need to make
the same change to avoid warnings and to support 64-bit machines. See the
earlier section <a class="reference internal" href="#pep-353">PEP 353: Using ssize_t as the index type</a> for a discussion of this change.</li>
<li>C API: The obmalloc changes mean that you must be careful to not mix usage
of the <tt class="xref c c-func docutils literal">PyMem_*()</tt> and <tt class="xref c c-func docutils literal">PyObject_*()</tt> families of functions. Memory
allocated with one family&#8217;s <tt class="xref c c-func docutils literal">*_Malloc()</tt> must be freed with the
corresponding family&#8217;s <tt class="xref c c-func docutils literal">*_Free()</tt> function.</li>
</ul>
</div>
<div class="section" id="acknowledgements">
<h2>Acknowledgements<a class="headerlink" href="#acknowledgements" title="Permalink to this headline">¶</a></h2>
The author would like to thank the following people for offering suggestions,
corrections and assistance with various drafts of this article: Georg Brandl,
Nick Coghlan, Phillip J. Eby, Lars Gustäbel, Raymond Hettinger, Ralf W. Grosse-
Kunstleve, Kent Johnson, Iain Lowe, Martin von Löwis, Fredrik Lundh, Andrew
McNamara, Skip Montanaro, Gustavo Niemeyer, Paul Prescod, James Pryor, Mike
Rovner, Scott Weikart, Barry Warsaw, Thomas Wouters.
</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="#">What&#8217;s New in Python 2.5</a><ul>
<li><a class="reference internal" href="#pep-308-conditional-expressions">PEP 308: Conditional Expressions</a></li>
<li><a class="reference internal" href="#pep-309-partial-function-application">PEP 309: Partial Function Application</a></li>
<li><a class="reference internal" href="#pep-314-metadata-for-python-software-packages-v1-1">PEP 314: Metadata for Python Software Packages v1.1</a></li>
<li><a class="reference internal" href="#pep-328-absolute-and-relative-imports">PEP 328: Absolute and Relative Imports</a></li>
<li><a class="reference internal" href="#pep-338-executing-modules-as-scripts">PEP 338: Executing Modules as Scripts</a></li>
<li><a class="reference internal" href="#pep-341-unified-try-except-finally">PEP 341: Unified try/except/finally</a></li>
<li><a class="reference internal" href="#pep-342-new-generator-features">PEP 342: New Generator Features</a></li>
<li><a class="reference internal" href="#pep-343-the-with-statement">PEP 343: The &#8216;with&#8217; statement</a><ul>
<li><a class="reference internal" href="#writing-context-managers">Writing Context Managers</a></li>
<li><a class="reference internal" href="#the-contextlib-module">The contextlib module</a></li>
</ul>
</li>
<li><a class="reference internal" href="#pep-352-exceptions-as-new-style-classes">PEP 352: Exceptions as New-Style Classes</a></li>
<li><a class="reference internal" href="#pep-353-using-ssize-t-as-the-index-type">PEP 353: Using ssize_t as the index type</a></li>
<li><a class="reference internal" href="#pep-357-the-index-method">PEP 357: The &#8216;__index__&#8217; method</a></li>
<li><a class="reference internal" href="#other-language-changes">Other Language Changes</a><ul>
<li><a class="reference internal" href="#interactive-interpreter-changes">Interactive Interpreter Changes</a></li>
<li><a class="reference internal" href="#optimizations">Optimizations</a></li>
</ul>
</li>
<li><a class="reference internal" href="#new-improved-and-removed-modules">New, Improved, and Removed Modules</a><ul>
<li><a class="reference internal" href="#the-ctypes-package">The ctypes package</a></li>
<li><a class="reference internal" href="#the-elementtree-package">The ElementTree package</a></li>
<li><a class="reference internal" href="#the-hashlib-package">The hashlib package</a></li>
<li><a class="reference internal" href="#the-sqlite3-package">The sqlite3 package</a></li>
<li><a class="reference internal" href="#the-wsgiref-package">The wsgiref package</a></li>
</ul>
</li>
<li><a class="reference internal" href="#build-and-c-api-changes">Build and C API Changes</a><ul>
<li><a class="reference internal" href="#port-specific-changes">Port-Specific Changes</a></li>
</ul>
</li>
<li><a class="reference internal" href="#porting-to-python-2-5">Porting to Python 2.5</a></li>
<li><a class="reference internal" href="#acknowledgements">Acknowledgements</a></li>
</ul>
</li>
</ul>

<h4>Previous topic</h4>
 <a href="2.6.html"
 title="previous chapter">What&#8217;s New in Python 2.6</a>
 <h4>Next topic</h4>
 <a href="2.4.html"
 title="next chapter">What&#8217;s New in Python 2.4</a>
<h3>This Page</h3>
<ul class="this-page-menu">
 <li><a href="../bugs.html">Report a Bug</a></li>
 <li><a href="../_sources/whatsnew/2.5.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="2.4.html" title="What’s New in Python 2.4"
 >next</a> |</li>
 <li class="right" >
 <a href="2.6.html" title="What’s New in Python 2.6"
 >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" >What&#8217;s New in Python</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>