Admin Control Panel v2.0

✎ Editing: descriptor.html ← Back

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

<html xmlns="http://www.w3.org/1999/xhtml">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 
 <title>Descriptor HowTo Guide &mdash; Python 2.7.5 documentation</title>
 
 <link rel="stylesheet" href="../_static/default.css" type="text/css" />
 <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
 
 <script type="text/javascript">
 var DOCUMENTATION_OPTIONS = {
 URL_ROOT: '../',
 VERSION: '2.7.5',
 COLLAPSE_INDEX: false,
 FILE_SUFFIX: '.html',
 HAS_SOURCE: true
 };
 </script>
 <script type="text/javascript" src="../_static/jquery.js"></script>
 <script type="text/javascript" src="../_static/underscore.js"></script>
 <script type="text/javascript" src="../_static/doctools.js"></script>
 <script type="text/javascript" src="../_static/sidebar.js"></script>
 <link rel="search" type="application/opensearchdescription+xml"
 title="Search within Python 2.7.5 documentation"
 href="../_static/opensearch.xml"/>
 <link rel="author" title="About these documents" href="../about.html" />
 <link rel="copyright" title="Copyright" href="../copyright.html" />
 <link rel="top" title="Python 2.7.5 documentation" href="../index.html" />
 <link rel="up" title="Python HOWTOs" href="index.html" />
 <link rel="next" title="Idioms and Anti-Idioms in Python" href="doanddont.html" />
 <link rel="prev" title="Curses Programming with Python" href="curses.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="doanddont.html" title="Idioms and Anti-Idioms in Python"
 accesskey="N">next</a> |</li>
 <li class="right" >
 <a href="curses.html" title="Curses Programming with Python"
 accesskey="P">previous</a> |</li>
 <li><img src="../_static/py.png" alt=""
 style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="http://www.python.org/">Python</a> &raquo;</li>
 <li>
 <a href="../index.html">Python 2.7.5 documentation</a> &raquo;
 </li>

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

<div class="document">
 <div class="documentwrapper">
 <div class="bodywrapper">
 <div class="body">
 
 <div class="section" id="descriptor-howto-guide">
<h1><a class="toc-backref" href="#id1">Descriptor HowTo Guide</a><a class="headerlink" href="#descriptor-howto-guide" 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">Raymond Hettinger</td>
</tr>
<tr class="field-even field"><th class="field-name">Contact:</th><td class="field-body">&lt;python at rcn dot com&gt;</td>
</tr>
</tbody>
</table>
<div class="contents topic" id="contents">
Contents
<ul class="simple">
<li><a class="reference internal" href="#descriptor-howto-guide" id="id1">Descriptor HowTo Guide</a><ul>
<li><a class="reference internal" href="#abstract" id="id2">Abstract</a></li>
<li><a class="reference internal" href="#definition-and-introduction" id="id3">Definition and Introduction</a></li>
<li><a class="reference internal" href="#descriptor-protocol" id="id4">Descriptor Protocol</a></li>
<li><a class="reference internal" href="#invoking-descriptors" id="id5">Invoking Descriptors</a></li>
<li><a class="reference internal" href="#descriptor-example" id="id6">Descriptor Example</a></li>
<li><a class="reference internal" href="#properties" id="id7">Properties</a></li>
<li><a class="reference internal" href="#functions-and-methods" id="id8">Functions and Methods</a></li>
<li><a class="reference internal" href="#static-methods-and-class-methods" id="id9">Static Methods and Class Methods</a></li>
</ul>
</li>
</ul>
</div>
<div class="section" id="abstract">
<h2><a class="toc-backref" href="#id2">Abstract</a><a class="headerlink" href="#abstract" title="Permalink to this headline">¶</a></h2>
Defines descriptors, summarizes the protocol, and shows how descriptors are
called. Examines a custom descriptor and several built-in python descriptors
including functions, properties, static methods, and class methods. Shows how
each works by giving a pure Python equivalent and a sample application.
Learning about descriptors not only provides access to a larger toolset, it
creates a deeper understanding of how Python works and an appreciation for the
elegance of its design.
</div>
<div class="section" id="definition-and-introduction">
<h2><a class="toc-backref" href="#id3">Definition and Introduction</a><a class="headerlink" href="#definition-and-introduction" title="Permalink to this headline">¶</a></h2>
In general, a descriptor is an object attribute with &#8220;binding behavior&#8221;, one
whose attribute access has been overridden by methods in the descriptor
protocol. Those methods are <a class="reference internal" href="../reference/datamodel.html#object.__get__" title="object.__get__"><tt class="xref py py-meth docutils literal">__get__()</tt></a>, <a class="reference internal" href="../reference/datamodel.html#object.__set__" title="object.__set__"><tt class="xref py py-meth docutils literal">__set__()</tt></a>, and
<a class="reference internal" href="../reference/datamodel.html#object.__delete__" title="object.__delete__"><tt class="xref py py-meth docutils literal">__delete__()</tt></a>. If any of those methods are defined for an object, it is
said to be a descriptor.
The default behavior for attribute access is to get, set, or delete the
attribute from an object&#8217;s dictionary. For instance, <tt class="docutils literal">a.x</tt> has a lookup chain
starting with <tt class="docutils literal">a.__dict__['x']</tt>, then <tt class="docutils literal">type(a).__dict__['x']</tt>, and
continuing through the base classes of <tt class="docutils literal">type(a)</tt> excluding metaclasses. If the
looked-up value is an object defining one of the descriptor methods, then Python
may override the default behavior and invoke the descriptor method instead.
Where this occurs in the precedence chain depends on which descriptor methods
were defined. Note that descriptors are only invoked for new style objects or
classes (a class is new style if it inherits from <a class="reference internal" href="../library/functions.html#object" title="object"><tt class="xref py py-class docutils literal">object</tt></a> or
<a class="reference internal" href="../library/functions.html#type" title="type"><tt class="xref py py-class docutils literal">type</tt></a>).
Descriptors are a powerful, general purpose protocol. They are the mechanism
behind properties, methods, static methods, class methods, and <a class="reference internal" href="../library/functions.html#super" title="super"><tt class="xref py py-func docutils literal">super()</tt></a>.
They are used throughout Python itself to implement the new style classes
introduced in version 2.2. Descriptors simplify the underlying C-code and offer
a flexible set of new tools for everyday Python programs.
</div>
<div class="section" id="descriptor-protocol">
<h2><a class="toc-backref" href="#id4">Descriptor Protocol</a><a class="headerlink" href="#descriptor-protocol" title="Permalink to this headline">¶</a></h2>
<tt class="docutils literal">descr.__get__(self, obj, type=None) --&gt; value</tt>
<tt class="docutils literal">descr.__set__(self, obj, value) --&gt; None</tt>
<tt class="docutils literal">descr.__delete__(self, obj) --&gt; None</tt>
That is all there is to it. Define any of these methods and an object is
considered a descriptor and can override default behavior upon being looked up
as an attribute.
If an object defines both <a class="reference internal" href="../reference/datamodel.html#object.__get__" title="object.__get__"><tt class="xref py py-meth docutils literal">__get__()</tt></a> and <a class="reference internal" href="../reference/datamodel.html#object.__set__" title="object.__set__"><tt class="xref py py-meth docutils literal">__set__()</tt></a>, it is considered
a data descriptor. Descriptors that only define <a class="reference internal" href="../reference/datamodel.html#object.__get__" title="object.__get__"><tt class="xref py py-meth docutils literal">__get__()</tt></a> are called
non-data descriptors (they are typically used for methods but other uses are
possible).
Data and non-data descriptors differ in how overrides are calculated with
respect to entries in an instance&#8217;s dictionary. If an instance&#8217;s dictionary
has an entry with the same name as a data descriptor, the data descriptor
takes precedence. If an instance&#8217;s dictionary has an entry with the same
name as a non-data descriptor, the dictionary entry takes precedence.
To make a read-only data descriptor, define both <a class="reference internal" href="../reference/datamodel.html#object.__get__" title="object.__get__"><tt class="xref py py-meth docutils literal">__get__()</tt></a> and
<a class="reference internal" href="../reference/datamodel.html#object.__set__" title="object.__set__"><tt class="xref py py-meth docutils literal">__set__()</tt></a> with the <a class="reference internal" href="../reference/datamodel.html#object.__set__" title="object.__set__"><tt class="xref py py-meth docutils literal">__set__()</tt></a> raising an <a class="reference internal" href="../library/exceptions.html#exceptions.AttributeError" title="exceptions.AttributeError"><tt class="xref py py-exc docutils literal">AttributeError</tt></a> when
called. Defining the <a class="reference internal" href="../reference/datamodel.html#object.__set__" title="object.__set__"><tt class="xref py py-meth docutils literal">__set__()</tt></a> method with an exception raising
placeholder is enough to make it a data descriptor.
</div>
<div class="section" id="invoking-descriptors">
<h2><a class="toc-backref" href="#id5">Invoking Descriptors</a><a class="headerlink" href="#invoking-descriptors" title="Permalink to this headline">¶</a></h2>
A descriptor can be called directly by its method name. For example,
<tt class="docutils literal">d.__get__(obj)</tt>.
Alternatively, it is more common for a descriptor to be invoked automatically
upon attribute access. For example, <tt class="docutils literal">obj.d</tt> looks up <tt class="docutils literal">d</tt> in the dictionary
of <tt class="docutils literal">obj</tt>. If <tt class="docutils literal">d</tt> defines the method <a class="reference internal" href="../reference/datamodel.html#object.__get__" title="object.__get__"><tt class="xref py py-meth docutils literal">__get__()</tt></a>, then <tt class="docutils literal">d.__get__(obj)</tt>
is invoked according to the precedence rules listed below.
The details of invocation depend on whether <tt class="docutils literal">obj</tt> is an object or a class.
Either way, descriptors only work for new style objects and classes. A class is
new style if it is a subclass of <a class="reference internal" href="../library/functions.html#object" title="object"><tt class="xref py py-class docutils literal">object</tt></a>.
For objects, the machinery is in <a class="reference internal" href="../reference/datamodel.html#object.__getattribute__" title="object.__getattribute__"><tt class="xref py py-meth docutils literal">object.__getattribute__()</tt></a> which
transforms <tt class="docutils literal">b.x</tt> into <tt class="docutils literal">type(b).__dict__['x'].__get__(b, type(b))</tt>. The
implementation works through a precedence chain that gives data descriptors
priority over instance variables, instance variables priority over non-data
descriptors, and assigns lowest priority to <a class="reference internal" href="../reference/datamodel.html#object.__getattr__" title="object.__getattr__"><tt class="xref py py-meth docutils literal">__getattr__()</tt></a> if provided. The
full C implementation can be found in <a class="reference internal" href="../c-api/object.html#PyObject_GenericGetAttr" title="PyObject_GenericGetAttr"><tt class="xref c c-func docutils literal">PyObject_GenericGetAttr()</tt></a> in
<a class="reference external" href="http://svn.python.org/view/python/trunk/Objects/object.c?view=markup">Objects/object.c</a>.
For classes, the machinery is in <tt class="xref py py-meth docutils literal">type.__getattribute__()</tt> which transforms
<tt class="docutils literal">B.x</tt> into <tt class="docutils literal">B.__dict__['x'].__get__(None, B)</tt>. In pure Python, it looks
like:
<div class="highlight-python"><div class="highlight"><pre>def __getattribute__(self, key):
 &quot;Emulate type_getattro() in Objects/typeobject.c&quot;
 v = object.__getattribute__(self, key)
 if hasattr(v, &#39;__get__&#39;):
 return v.__get__(None, self)
 return v
</pre></div>
</div>
The important points to remember are:
<ul class="simple">
<li>descriptors are invoked by the <a class="reference internal" href="../reference/datamodel.html#object.__getattribute__" title="object.__getattribute__"><tt class="xref py py-meth docutils literal">__getattribute__()</tt></a> method</li>
<li>overriding <a class="reference internal" href="../reference/datamodel.html#object.__getattribute__" title="object.__getattribute__"><tt class="xref py py-meth docutils literal">__getattribute__()</tt></a> prevents automatic descriptor calls</li>
<li><a class="reference internal" href="../reference/datamodel.html#object.__getattribute__" title="object.__getattribute__"><tt class="xref py py-meth docutils literal">__getattribute__()</tt></a> is only available with new style classes and objects</li>
<li><a class="reference internal" href="../reference/datamodel.html#object.__getattribute__" title="object.__getattribute__"><tt class="xref py py-meth docutils literal">object.__getattribute__()</tt></a> and <tt class="xref py py-meth docutils literal">type.__getattribute__()</tt> make
different calls to <a class="reference internal" href="../reference/datamodel.html#object.__get__" title="object.__get__"><tt class="xref py py-meth docutils literal">__get__()</tt></a>.</li>
<li>data descriptors always override instance dictionaries.</li>
<li>non-data descriptors may be overridden by instance dictionaries.</li>
</ul>
The object returned by <tt class="docutils literal">super()</tt> also has a custom <a class="reference internal" href="../reference/datamodel.html#object.__getattribute__" title="object.__getattribute__"><tt class="xref py py-meth docutils literal">__getattribute__()</tt></a>
method for invoking descriptors. The call <tt class="docutils literal">super(B, obj).m()</tt> searches
<tt class="docutils literal">obj.__class__.__mro__</tt> for the base class <tt class="docutils literal">A</tt> immediately following <tt class="docutils literal">B</tt>
and then returns <tt class="docutils literal">A.__dict__['m'].__get__(obj, A)</tt>. If not a descriptor,
<tt class="docutils literal">m</tt> is returned unchanged. If not in the dictionary, <tt class="docutils literal">m</tt> reverts to a
search using <a class="reference internal" href="../reference/datamodel.html#object.__getattribute__" title="object.__getattribute__"><tt class="xref py py-meth docutils literal">object.__getattribute__()</tt></a>.
Note, in Python 2.2, <tt class="docutils literal">super(B, obj).m()</tt> would only invoke <a class="reference internal" href="../reference/datamodel.html#object.__get__" title="object.__get__"><tt class="xref py py-meth docutils literal">__get__()</tt></a> if
<tt class="docutils literal">m</tt> was a data descriptor. In Python 2.3, non-data descriptors also get
invoked unless an old-style class is involved. The implementation details are
in <tt class="xref c c-func docutils literal">super_getattro()</tt> in
<a class="reference external" href="http://svn.python.org/view/python/trunk/Objects/typeobject.c?view=markup">Objects/typeobject.c</a>
and a pure Python equivalent can be found in <a class="reference external" href="http://www.python.org/2.2.3/descrintro.html#cooperation">Guido&#8217;s Tutorial</a>.
The details above show that the mechanism for descriptors is embedded in the
<a class="reference internal" href="../reference/datamodel.html#object.__getattribute__" title="object.__getattribute__"><tt class="xref py py-meth docutils literal">__getattribute__()</tt></a> methods for <a class="reference internal" href="../library/functions.html#object" title="object"><tt class="xref py py-class docutils literal">object</tt></a>, <a class="reference internal" href="../library/functions.html#type" title="type"><tt class="xref py py-class docutils literal">type</tt></a>, and
<a class="reference internal" href="../library/functions.html#super" title="super"><tt class="xref py py-func docutils literal">super()</tt></a>. Classes inherit this machinery when they derive from
<a class="reference internal" href="../library/functions.html#object" title="object"><tt class="xref py py-class docutils literal">object</tt></a> or if they have a meta-class providing similar functionality.
Likewise, classes can turn-off descriptor invocation by overriding
<a class="reference internal" href="../reference/datamodel.html#object.__getattribute__" title="object.__getattribute__"><tt class="xref py py-meth docutils literal">__getattribute__()</tt></a>.
</div>
<div class="section" id="descriptor-example">
<h2><a class="toc-backref" href="#id6">Descriptor Example</a><a class="headerlink" href="#descriptor-example" title="Permalink to this headline">¶</a></h2>
The following code creates a class whose objects are data descriptors which
print a message for each get or set. Overriding <a class="reference internal" href="../reference/datamodel.html#object.__getattribute__" title="object.__getattribute__"><tt class="xref py py-meth docutils literal">__getattribute__()</tt></a> is
alternate approach that could do this for every attribute. However, this
descriptor is useful for monitoring just a few chosen attributes:
<div class="highlight-python"><pre>class RevealAccess(object):
 """A data descriptor that sets and returns values
 normally and prints a message logging their access.
 """

def __init__(self, initval=None, name='var'):
        self.val = initval
        self.name = name

def __get__(self, obj, objtype):
        print 'Retrieving', self.name
        return self.val

def __set__(self, obj, val):
        print 'Updating' , self.name
        self.val = val

&gt;&gt;&gt; class MyClass(object):
    x = RevealAccess(10, 'var "x"')
    y = 5

&gt;&gt;&gt; m = MyClass()
&gt;&gt;&gt; m.x
Retrieving var "x"
10
&gt;&gt;&gt; m.x = 20
Updating var "x"
&gt;&gt;&gt; m.x
Retrieving var "x"
20
&gt;&gt;&gt; m.y
5</pre>
</div>
The protocol is simple and offers exciting possibilities. Several use cases are
so common that they have been packaged into individual function calls.
Properties, bound and unbound methods, static methods, and class methods are all
based on the descriptor protocol.
</div>
<div class="section" id="properties">
<h2><a class="toc-backref" href="#id7">Properties</a><a class="headerlink" href="#properties" title="Permalink to this headline">¶</a></h2>
Calling <a class="reference internal" href="../library/functions.html#property" title="property"><tt class="xref py py-func docutils literal">property()</tt></a> is a succinct way of building a data descriptor that
triggers function calls upon access to an attribute. Its signature is:
<div class="highlight-python"><pre>property(fget=None, fset=None, fdel=None, doc=None) -&gt; property attribute</pre>
</div>
The documentation shows a typical use to define a managed attribute <tt class="docutils literal">x</tt>:
<div class="highlight-python"><div class="highlight"><pre>class C(object):
 def getx(self): return self.__x
 def setx(self, value): self.__x = value
 def delx(self): del self.__x
 x = property(getx, setx, delx, &quot;I&#39;m the &#39;x&#39; property.&quot;)
</pre></div>
</div>
To see how <a class="reference internal" href="../library/functions.html#property" title="property"><tt class="xref py py-func docutils literal">property()</tt></a> is implemented in terms of the descriptor protocol,
here is a pure Python equivalent:
<div class="highlight-python"><div class="highlight"><pre>class Property(object):
 &quot;Emulate PyProperty_Type() in Objects/descrobject.c&quot;

def __init__(self, fget=None, fset=None, fdel=None, doc=None):
 self.fget = fget
 self.fset = fset
 self.fdel = fdel
 if doc is None and fget is not None:
 doc = fget.__doc__
 self.__doc__ = doc

def __get__(self, obj, objtype=None):
 if obj is None:
 return self
 if self.fget is None:
 raise AttributeError(&quot;unreadable attribute&quot;)
 return self.fget(obj)

def __set__(self, obj, value):
 if self.fset is None:
 raise AttributeError(&quot;can&#39;t set attribute&quot;)
 self.fset(obj, value)

def __delete__(self, obj):
 if self.fdel is None:
 raise AttributeError(&quot;can&#39;t delete attribute&quot;)
 self.fdel(obj)

def getter(self, fget):
 return type(self)(fget, self.fset, self.fdel, self.__doc__)

def setter(self, fset):
 return type(self)(self.fget, fset, self.fdel, self.__doc__)

def deleter(self, fdel):
 return type(self)(self.fget, self.fset, fdel, self.__doc__)
</pre></div>
</div>
The <a class="reference internal" href="../library/functions.html#property" title="property"><tt class="xref py py-func docutils literal">property()</tt></a> builtin helps whenever a user interface has granted
attribute access and then subsequent changes require the intervention of a
method.
For instance, a spreadsheet class may grant access to a cell value through
<tt class="docutils literal">Cell('b10').value</tt>. Subsequent improvements to the program require the cell
to be recalculated on every access; however, the programmer does not want to
affect existing client code accessing the attribute directly. The solution is
to wrap access to the value attribute in a property data descriptor:
<div class="highlight-python"><pre>class Cell(object):
 . . .
 def getvalue(self, obj):
 "Recalculate cell before returning value"
 self.recalc()
 return obj._value
 value = property(getvalue)</pre>
</div>
</div>
<div class="section" id="functions-and-methods">
<h2><a class="toc-backref" href="#id8">Functions and Methods</a><a class="headerlink" href="#functions-and-methods" title="Permalink to this headline">¶</a></h2>
Python&#8217;s object oriented features are built upon a function based environment.
Using non-data descriptors, the two are merged seamlessly.
Class dictionaries store methods as functions. In a class definition, methods
are written using <a class="reference internal" href="../reference/compound_stmts.html#def"><tt class="xref std std-keyword docutils literal">def</tt></a> and <a class="reference internal" href="../reference/expressions.html#lambda"><tt class="xref std std-keyword docutils literal">lambda</tt></a>, the usual tools for
creating functions. The only difference from regular functions is that the
first argument is reserved for the object instance. By Python convention, the
instance reference is called self but may be called this or any other
variable name.
To support method calls, functions include the <a class="reference internal" href="../reference/datamodel.html#object.__get__" title="object.__get__"><tt class="xref py py-meth docutils literal">__get__()</tt></a> method for
binding methods during attribute access. This means that all functions are
non-data descriptors which return bound or unbound methods depending whether
they are invoked from an object or a class. In pure python, it works like
this:
<div class="highlight-python"><pre>class Function(object):
 . . .
 def __get__(self, obj, objtype=None):
 "Simulate func_descr_get() in Objects/funcobject.c"
 return types.MethodType(self, obj, objtype)</pre>
</div>
Running the interpreter shows how the function descriptor works in practice:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; class D(object):
 def f(self, x):
 return x

&gt;&gt;&gt; d = D()
&gt;&gt;&gt; D.__dict__[&#39;f&#39;] # Stored internally as a function
&lt;function f at 0x00C45070&gt;
&gt;&gt;&gt; D.f # Get from a class becomes an unbound method
&lt;unbound method D.f&gt;
&gt;&gt;&gt; d.f # Get from an instance becomes a bound method
&lt;bound method D.f of &lt;__main__.D object at 0x00B18C90&gt;&gt;
</pre></div>
</div>
The output suggests that bound and unbound methods are two different types.
While they could have been implemented that way, the actual C implementation of
<a class="reference internal" href="../c-api/method.html#PyMethod_Type" title="PyMethod_Type"><tt class="xref c c-type docutils literal">PyMethod_Type</tt></a> in
<a class="reference external" href="http://svn.python.org/view/python/trunk/Objects/classobject.c?view=markup">Objects/classobject.c</a>
is a single object with two different representations depending on whether the
<tt class="xref py py-attr docutils literal">im_self</tt> field is set or is NULL (the C equivalent of None).
Likewise, the effects of calling a method object depend on the <tt class="xref py py-attr docutils literal">im_self</tt>
field. If set (meaning bound), the original function (stored in the
<tt class="xref py py-attr docutils literal">im_func</tt> field) is called as expected with the first argument set to the
instance. If unbound, all of the arguments are passed unchanged to the original
function. The actual C implementation of <tt class="xref py py-func docutils literal">instancemethod_call()</tt> is only
slightly more complex in that it includes some type checking.
</div>
<div class="section" id="static-methods-and-class-methods">
<h2><a class="toc-backref" href="#id9">Static Methods and Class Methods</a><a class="headerlink" href="#static-methods-and-class-methods" title="Permalink to this headline">¶</a></h2>
Non-data descriptors provide a simple mechanism for variations on the usual
patterns of binding functions into methods.
To recap, functions have a <a class="reference internal" href="../reference/datamodel.html#object.__get__" title="object.__get__"><tt class="xref py py-meth docutils literal">__get__()</tt></a> method so that they can be converted
to a method when accessed as attributes. The non-data descriptor transforms a
<tt class="docutils literal">obj.f(*args)</tt> call into <tt class="docutils literal">f(obj, *args)</tt>. Calling <tt class="docutils literal">klass.f(*args)</tt>
becomes <tt class="docutils literal">f(*args)</tt>.
This chart summarizes the binding and its two most useful variants:
<blockquote>
<div><table border="1" class="docutils">
<colgroup>
<col width="30%" />
<col width="39%" />
<col width="32%" />
</colgroup>
<thead valign="bottom">
<tr class="row-odd"><th class="head">Transformation</th>
<th class="head">Called from an
Object</th>
<th class="head">Called from a
Class</th>
</tr>
</thead>
<tbody valign="top">
<tr class="row-even"><td>function</td>
<td>f(obj, *args)</td>
<td>f(*args)</td>
</tr>
<tr class="row-odd"><td>staticmethod</td>
<td>f(*args)</td>
<td>f(*args)</td>
</tr>
<tr class="row-even"><td>classmethod</td>
<td>f(type(obj), *args)</td>
<td>f(klass, *args)</td>
</tr>
</tbody>
</table>
</div></blockquote>
Static methods return the underlying function without changes. Calling either
<tt class="docutils literal">c.f</tt> or <tt class="docutils literal">C.f</tt> is the equivalent of a direct lookup into
<tt class="docutils literal">object.__getattribute__(c, &quot;f&quot;)</tt> or <tt class="docutils literal">object.__getattribute__(C, &quot;f&quot;)</tt>. As a
result, the function becomes identically accessible from either an object or a
class.
Good candidates for static methods are methods that do not reference the
<tt class="docutils literal">self</tt> variable.
For instance, a statistics package may include a container class for
experimental data. The class provides normal methods for computing the average,
mean, median, and other descriptive statistics that depend on the data. However,
there may be useful functions which are conceptually related but do not depend
on the data. For instance, <tt class="docutils literal">erf(x)</tt> is handy conversion routine that comes up
in statistical work but does not directly depend on a particular dataset.
It can be called either from an object or the class: <tt class="docutils literal">s.erf(1.5) --&gt; .9332</tt> or
<tt class="docutils literal">Sample.erf(1.5) --&gt; .9332</tt>.
Since staticmethods return the underlying function with no changes, the example
calls are unexciting:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; class E(object):
 def f(x):
 print x
 f = staticmethod(f)

def __init__(self, f):
 self.f = f

def __get__(self, obj, objtype=None):
 return self.f
</pre></div>
</div>
Unlike static methods, class methods prepend the class reference to the
argument list before calling the function. This format is the same
for whether the caller is an object or a class:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; class E(object):
 def f(klass, x):
 return klass.__name__, x
 f = classmethod(f)

&gt;&gt;&gt; print E.f(3)
(&#39;E&#39;, 3)
&gt;&gt;&gt; print E().f(3)
(&#39;E&#39;, 3)
</pre></div>
</div>
This behavior is useful whenever the function only needs to have a class
reference and does not care about any underlying data. One use for classmethods
is to create alternate class constructors. In Python 2.3, the classmethod
<a class="reference internal" href="../library/stdtypes.html#dict.fromkeys" title="dict.fromkeys"><tt class="xref py py-func docutils literal">dict.fromkeys()</tt></a> creates a new dictionary from a list of keys. The pure
Python equivalent is:
<div class="highlight-python"><pre>class Dict(object):
 . . .
 def fromkeys(klass, iterable, value=None):
 "Emulate dict_fromkeys() in Objects/dictobject.c"
 d = klass()
 for key in iterable:
 d[key] = value
 return d
 fromkeys = classmethod(fromkeys)</pre>
</div>
Now a new dictionary of unique keys can be constructed like this:
<div class="highlight-python"><div class="highlight"><pre>&gt;&gt;&gt; Dict.fromkeys(&#39;abracadabra&#39;)
{&#39;a&#39;: None, &#39;r&#39;: None, &#39;b&#39;: None, &#39;c&#39;: None, &#39;d&#39;: None}
</pre></div>
</div>
Using the non-data descriptor protocol, a pure Python version of
<a class="reference internal" href="../library/functions.html#classmethod" title="classmethod"><tt class="xref py py-func docutils literal">classmethod()</tt></a> would look like this:
<div class="highlight-python"><div class="highlight"><pre>class ClassMethod(object):
 &quot;Emulate PyClassMethod_Type() in Objects/funcobject.c&quot;

def __init__(self, f):
 self.f = f

def __get__(self, obj, klass=None):
 if klass is None:
 klass = type(obj)
 def newfunc(*args):
 return self.f(klass, *args)
 return newfunc
</pre></div>
</div>
</div>
</div>

</div>
 </div>
 </div>
 <div class="sphinxsidebar">
 <div class="sphinxsidebarwrapper">
 <h3><a href="../contents.html">Table Of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#">Descriptor HowTo Guide</a><ul>
<li><a class="reference internal" href="#abstract">Abstract</a></li>
<li><a class="reference internal" href="#definition-and-introduction">Definition and Introduction</a></li>
<li><a class="reference internal" href="#descriptor-protocol">Descriptor Protocol</a></li>
<li><a class="reference internal" href="#invoking-descriptors">Invoking Descriptors</a></li>
<li><a class="reference internal" href="#descriptor-example">Descriptor Example</a></li>
<li><a class="reference internal" href="#properties">Properties</a></li>
<li><a class="reference internal" href="#functions-and-methods">Functions and Methods</a></li>
<li><a class="reference internal" href="#static-methods-and-class-methods">Static Methods and Class Methods</a></li>
</ul>
</li>
</ul>

<h4>Previous topic</h4>
 <a href="curses.html"
 title="previous chapter">Curses Programming with Python</a>
 <h4>Next topic</h4>
 <a href="doanddont.html"
 title="next chapter">Idioms and Anti-Idioms in Python</a>
<h3>This Page</h3>
<ul class="this-page-menu">
 <li><a href="../bugs.html">Report a Bug</a></li>
 <li><a href="../_sources/howto/descriptor.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="doanddont.html" title="Idioms and Anti-Idioms in Python"
 >next</a> |</li>
 <li class="right" >
 <a href="curses.html" title="Curses Programming with Python"
 >previous</a> |</li>
 <li><img src="../_static/py.png" alt=""
 style="vertical-align: middle; margin-top: -1px"/></li>
 <li><a href="http://www.python.org/">Python</a> &raquo;</li>
 <li>
 <a href="../index.html">Python 2.7.5 documentation</a> &raquo;
 </li>

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

</body>
</html>

Cancel