Elep

<!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>
 
 
 Namespaces
 &mdash;
 Mako 1.1.0 Documentation

</title>

<link rel="stylesheet" href="_static/pygments.css" type="text/css" />
 <link rel="stylesheet" href="_static/changelog.css" type="text/css" />
 <link rel="stylesheet" href="_static/sphinx_paramlinks.css" type="text/css" />
 <link rel="stylesheet" href="_static/docs.css" type="text/css" />

</head>
 <body>

<div id="docs-header">
 <h1>Mako 1.1.0 Documentation</h1>

<div id="docs-search">
 Search:
 <form class="search" action="search.html" method="get">
 <input type="text" name="q" size="18" /> <input type="submit" value="Search" />
 <input type="hidden" name="check_keywords" value="yes" />
 <input type="hidden" name="area" value="default" />
 </form>
 </div>

<div id="docs-version-header">
 Release: 1.1.0

</div>

<div id="docs-top-navigation">
 <div id="docs-top-page-control" class="docs-navigation-links">
 <ul>
 <li>Prev:
 <a href="runtime.html" title="previous chapter">The Mako Runtime Environment</a>
 </li>
 <li>Next:
 <a href="inheritance.html" title="next chapter">Inheritance</a>
 </li>

<li>
 <a href="index.html">Table of Contents</a> |
 <a href="genindex.html">Index</a>
 </li>
 </ul>
 </div>

<div id="docs-navigation-banner">
 <a href="index.html">Mako 1.1.0 Documentation</a>
 » 
 Namespaces

<h2>
 
 Namespaces
 
 </h2>
 </div>

</div>

<h3><a href="index.html">Table of Contents</a></h3>
 <ul>
<li><a class="reference internal" href="#">Namespaces</a><ul>
<li><a class="reference internal" href="#ways-to-call-namespaces">Ways to Call Namespaces</a></li>
<li><a class="reference internal" href="#namespaces-from-regular-python-modules">Namespaces from Regular Python Modules</a></li>
<li><a class="reference internal" href="#declaring-defs-in-namespaces">Declaring Defs in Namespaces</a></li>
<li><a class="reference internal" href="#the-body-method">The <code class="docutils literal notranslate">body()</code> Method</a></li>
<li><a class="reference internal" href="#built-in-namespaces">Built-in Namespaces</a><ul>
<li><a class="reference internal" href="#local"><code class="docutils literal notranslate">local</code></a></li>
<li><a class="reference internal" href="#self"><code class="docutils literal notranslate">self</code></a></li>
</ul>
</li>
<li><a class="reference internal" href="#inheritable-namespaces">Inheritable Namespaces</a></li>
<li><a class="reference internal" href="#namespace-api-usage-example-static-dependencies">Namespace API Usage Example - Static Dependencies</a><ul>
<li><a class="reference internal" href="#version-one-use-namespace-attr">Version One - Use <code class="xref py py-attr docutils literal notranslate">Namespace.attr</code></a></li>
<li><a class="reference internal" href="#version-two-use-a-specific-named-def">Version Two - Use a specific named def</a></li>
</ul>
</li>
<li><a class="reference internal" href="#api-reference">API Reference</a></li>
</ul>
</li>
</ul>

<h4>Previous Topic</h4>
 
 <a href="runtime.html" title="previous chapter">The Mako Runtime Environment</a>
 
 <h4>Next Topic</h4>
 
 <a href="inheritance.html" title="next chapter">Inheritance</a>

<h4>Quick Search</h4>
 
 <form class="search" action="search.html" method="get">
 <input type="text" name="q" size="18" /> <input type="submit" value="Search" />
 <input type="hidden" name="check_keywords" value="yes" />
 <input type="hidden" name="area" value="default" />
 </form>

</div>

<div id="docs-body" class="withsidebar" >
 
<div class="section" id="namespaces">
<h1>Namespaces<a class="headerlink" href="#namespaces" title="Permalink to this headline">¶</a></h1>
Namespaces are used to organize groups of defs into
categories, and also to “import” defs from other files.
If the file <code class="docutils literal notranslate">components.html</code> defines these two defs:
<div class="highlight-mako notranslate"><div class="highlight"><pre>## components.html
&lt;%def name=&quot;comp1()&quot;&gt;
 this is comp1
&lt;/%def&gt;

&lt;%def name=&quot;comp2(x)&quot;&gt;
 this is comp2, x is ${x}
&lt;/%def&gt;</pre></div>
</div>
you can make another file, for example <code class="docutils literal notranslate">index.html</code>, that
pulls those two defs into a namespace called <code class="docutils literal notranslate">comp</code>:
<div class="highlight-mako notranslate"><div class="highlight"><pre>## index.html
&lt;%namespace name=&quot;comp&quot; file=&quot;components.html&quot;/&gt;

Here&#39;s comp1: ${comp.comp1()}
Here&#39;s comp2: ${comp.comp2(x=5)}</pre></div>
</div>
The <code class="docutils literal notranslate">comp</code> variable above is an instance of
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>, a proxy object which delivers
method calls to the underlying template callable using the
current context.
<code class="docutils literal notranslate">&lt;%namespace&gt;</code> also provides an <code class="docutils literal notranslate">import</code> attribute which can
be used to pull the names into the local namespace, removing the
need to call it via the “<code class="docutils literal notranslate">.</code>” operator. When <code class="docutils literal notranslate">import</code> is used, the
<code class="docutils literal notranslate">name</code> attribute is optional.
<div class="highlight-mako notranslate"><div class="highlight"><pre>&lt;%namespace file=&quot;components.html&quot; import=&quot;comp1, comp2&quot;/&gt;

Heres comp1: ${comp1()}
Heres comp2: ${comp2(x=5)}</pre></div>
</div>
The names imported by the <code class="docutils literal notranslate">import</code> attribute take precedence
over any names that exist within the current context.
<div class="admonition note">
Note
In current versions of Mako, usage of <code class="docutils literal notranslate">import='*'</code> is
known to decrease performance of the template. This will be
fixed in a future release.
</div>
The <code class="docutils literal notranslate">file</code> argument allows expressions – if looking for
context variables, the <code class="docutils literal notranslate">context</code> must be named explicitly:
<div class="highlight-mako notranslate"><div class="highlight"><pre>&lt;%namespace name=&quot;dyn&quot; file=&quot;${context[&#39;namespace_name&#39;]}&quot;/&gt;</pre></div>
</div>
<div class="section" id="ways-to-call-namespaces">
<h2>Ways to Call Namespaces<a class="headerlink" href="#ways-to-call-namespaces" title="Permalink to this headline">¶</a></h2>
There are essentially four ways to call a function from a
namespace.
The “expression” format, as described previously. Namespaces are
just Python objects with functions on them, and can be used in
expressions like any other function:
<div class="highlight-mako notranslate"><div class="highlight"><pre>${mynamespace.somefunction(&#39;some arg1&#39;, &#39;some arg2&#39;, arg3=&#39;some arg3&#39;, arg4=&#39;some arg4&#39;)}</pre></div>
</div>
Synonymous with the “expression” format is the “custom tag”
format, when a “closed” tag is used. This format, introduced in
Mako 0.2.3, allows the usage of a “custom” Mako tag, with the
function arguments passed in using named attributes:
<div class="highlight-mako notranslate"><div class="highlight"><pre>&lt;%mynamespace:somefunction arg1=&quot;some arg1&quot; arg2=&quot;some arg2&quot; arg3=&quot;some arg3&quot; arg4=&quot;some arg4&quot;/&gt;</pre></div>
</div>
When using tags, the values of the arguments are taken as
literal strings by default. To embed Python expressions as
arguments, use the embedded expression format:
<div class="highlight-mako notranslate"><div class="highlight"><pre>&lt;%mynamespace:somefunction arg1=&quot;${someobject.format()}&quot; arg2=&quot;${somedef(5, 12)}&quot;/&gt;</pre></div>
</div>
The “custom tag” format is intended mainly for namespace
functions which recognize body content, which in Mako is known
as a “def with embedded content”:
<div class="highlight-mako notranslate"><div class="highlight"><pre>&lt;%mynamespace:somefunction arg1=&quot;some argument&quot; args=&quot;x, y&quot;&gt;
 Some record: ${x}, ${y}
&lt;/%mynamespace:somefunction&gt;</pre></div>
</div>
The “classic” way to call defs with embedded content is the <code class="docutils literal notranslate">&lt;%call&gt;</code> tag:
<div class="highlight-mako notranslate"><div class="highlight"><pre>&lt;%call expr=&quot;mynamespace.somefunction(arg1=&#39;some argument&#39;)&quot; args=&quot;x, y&quot;&gt;
 Some record: ${x}, ${y}
&lt;/%call&gt;</pre></div>
</div>
For information on how to construct defs that embed content from
the caller, see <a class="reference internal" href="defs.html#defs-with-content">Calling a Def with Embedded Content and/or Other Defs</a>.
</div>
<div class="section" id="namespaces-from-regular-python-modules">
<h2>Namespaces from Regular Python Modules<a class="headerlink" href="#namespaces-from-regular-python-modules" title="Permalink to this headline">¶</a></h2>
Namespaces can also import regular Python functions from
modules. These callables need to take at least one argument,
<code class="docutils literal notranslate">context</code>, an instance of <a class="reference internal" href="runtime.html#mako.runtime.Context" title="mako.runtime.Context"><code class="xref py py-class docutils literal notranslate">Context</code></a>. A module file
<code class="docutils literal notranslate">some/module.py</code> might contain the callable:
<div class="highlight-python notranslate"><div class="highlight"><pre>def my_tag(context):
 context.write(&quot;hello world&quot;)
 return &#39;&#39;</pre></div>
</div>
A template can use this module via:
<div class="highlight-mako notranslate"><div class="highlight"><pre>&lt;%namespace name=&quot;hw&quot; module=&quot;some.module&quot;/&gt;

${hw.my_tag()}</pre></div>
</div>
Note that the <code class="docutils literal notranslate">context</code> argument is not needed in the call;
the <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> tag creates a locally-scoped callable which
takes care of it. The <code class="docutils literal notranslate">return ''</code> is so that the def does not
dump a <code class="docutils literal notranslate">None</code> into the output stream – the return value of any
def is rendered after the def completes, in addition to whatever
was passed to <a class="reference internal" href="runtime.html#mako.runtime.Context.write" title="mako.runtime.Context.write"><code class="xref py py-meth docutils literal notranslate">Context.write()</code></a> within its body.
If your def is to be called in an “embedded content” context,
that is as described in <a class="reference internal" href="defs.html#defs-with-content">Calling a Def with Embedded Content and/or Other Defs</a>, you should use
the <a class="reference internal" href="#mako.runtime.supports_caller" title="mako.runtime.supports_caller"><code class="xref py py-func docutils literal notranslate">supports_caller()</code></a> decorator, which will ensure that Mako
will ensure the correct “caller” variable is available when your
def is called, supporting embedded content:
<div class="highlight-python notranslate"><div class="highlight"><pre>from mako.runtime import supports_caller

@supports_caller
def my_tag(context):
 return &quot;&lt;div&gt;%s&lt;/div&gt;&quot; % \
 capture(context, context[&#39;caller&#39;].body, x=&quot;foo&quot;, y=&quot;bar&quot;)</pre></div>
</div>
</div>
<div class="section" id="declaring-defs-in-namespaces">
<h2>Declaring Defs in Namespaces<a class="headerlink" href="#declaring-defs-in-namespaces" title="Permalink to this headline">¶</a></h2>
The <code class="docutils literal notranslate">&lt;%namespace&gt;</code> tag supports the definition of <code class="docutils literal notranslate">&lt;%def&gt;</code>s
directly inside the tag. These defs become part of the namespace
like any other function, and will override the definitions
pulled in from a remote template or module:
<div class="highlight-mako notranslate"><div class="highlight"><pre>## define a namespace
&lt;%namespace name=&quot;stuff&quot;&gt;
 &lt;%def name=&quot;comp1()&quot;&gt;
 comp1
 &lt;/%def&gt;
&lt;/%namespace&gt;

## then call it
${stuff.comp1()}</pre></div>
</div>
</div>
<div class="section" id="the-body-method">
<h2>The <code class="docutils literal notranslate">body()</code> Method<a class="headerlink" href="#the-body-method" title="Permalink to this headline">¶</a></h2>
Every namespace that is generated from a template contains a
method called <code class="docutils literal notranslate">body()</code>. This method corresponds to the main
body of the template, and plays its most important roles when
using inheritance relationships as well as
def-calls-with-content.
Since the <code class="docutils literal notranslate">body()</code> method is available from a namespace just
like all the other defs defined in a template, what happens if
you send arguments to it? By default, the <code class="docutils literal notranslate">body()</code> method
accepts no positional arguments, and for usefulness in
inheritance scenarios will by default dump all keyword arguments
into a dictionary called <code class="docutils literal notranslate">pageargs</code>. But if you actually want
to get at the keyword arguments, Mako recommends you define your
own argument signature explicitly. You do this via using the
<code class="docutils literal notranslate">&lt;%page&gt;</code> tag:
<div class="highlight-mako notranslate"><div class="highlight"><pre>&lt;%page args=&quot;x, y, someval=8, scope=&#39;foo&#39;, **kwargs&quot;/&gt;</pre></div>
</div>
A template which defines the above signature requires that the
variables <code class="docutils literal notranslate">x</code> and <code class="docutils literal notranslate">y</code> are defined, defines default values
for <code class="docutils literal notranslate">someval</code> and <code class="docutils literal notranslate">scope</code>, and sets up <code class="docutils literal notranslate">**kwargs</code> to
receive all other keyword arguments. If <code class="docutils literal notranslate">**kwargs</code> or similar
is not present, the argument <code class="docutils literal notranslate">**pageargs</code> gets tacked on by
Mako. When the template is called as a top-level template (i.e.
via <a class="reference internal" href="usage.html#mako.template.Template.render" title="mako.template.Template.render"><code class="xref py py-meth docutils literal notranslate">render()</code></a>) or via the <code class="docutils literal notranslate">&lt;%include&gt;</code> tag, the
values for these arguments will be pulled from the <code class="docutils literal notranslate">Context</code>.
In all other cases, i.e. via calling the <code class="docutils literal notranslate">body()</code> method, the
arguments are taken as ordinary arguments from the method call.
So above, the body might be called as:
<div class="highlight-mako notranslate"><div class="highlight"><pre>${self.body(5, y=10, someval=15, delta=7)}</pre></div>
</div>
The <a class="reference internal" href="runtime.html#mako.runtime.Context" title="mako.runtime.Context"><code class="xref py py-class docutils literal notranslate">Context</code></a> object also supplies a <code class="xref py py-attr docutils literal notranslate">kwargs</code>
accessor, for cases when you’d like to pass along the top level context
arguments to a <code class="docutils literal notranslate">body()</code> callable:
<div class="highlight-mako notranslate"><div class="highlight"><pre>${next.body(**context.kwargs)}</pre></div>
</div>
The usefulness of calls like the above become more apparent when
one works with inheriting templates. For more information on
this, as well as the meanings of the names <code class="docutils literal notranslate">self</code> and
<code class="docutils literal notranslate">next</code>, see <a class="reference internal" href="inheritance.html">Inheritance</a>.
</div>
<div class="section" id="built-in-namespaces">
<h2>Built-in Namespaces<a class="headerlink" href="#built-in-namespaces" title="Permalink to this headline">¶</a></h2>
The namespace is so great that Mako gives your template one (or
two) for free. The names of these namespaces are <code class="docutils literal notranslate">local</code> and
<code class="docutils literal notranslate">self</code>. Other built-in namespaces include <code class="docutils literal notranslate">parent</code> and
<code class="docutils literal notranslate">next</code>, which are optional and are described in
<a class="reference internal" href="inheritance.html">Inheritance</a>.
<div class="section" id="local">
<h3><code class="docutils literal notranslate">local</code><a class="headerlink" href="#local" title="Permalink to this headline">¶</a></h3>
The <code class="docutils literal notranslate">local</code> namespace is basically the namespace for the
currently executing template. This means that all of the top
level defs defined in your template, as well as your template’s
<code class="docutils literal notranslate">body()</code> function, are also available off of the <code class="docutils literal notranslate">local</code>
namespace.
The <code class="docutils literal notranslate">local</code> namespace is also where properties like <code class="docutils literal notranslate">uri</code>,
<code class="docutils literal notranslate">filename</code>, and <code class="docutils literal notranslate">module</code> and the <code class="docutils literal notranslate">get_namespace</code> method
can be particularly useful.
</div>
<div class="section" id="self">
<h3><code class="docutils literal notranslate">self</code><a class="headerlink" href="#self" title="Permalink to this headline">¶</a></h3>
The <code class="docutils literal notranslate">self</code> namespace, in the case of a template that does not
use inheritance, is synonymous with <code class="docutils literal notranslate">local</code>. If inheritance is
used, then <code class="docutils literal notranslate">self</code> references the topmost template in the
inheritance chain, where it is most useful for providing the
ultimate form of various “method” calls which may have been
overridden at various points in an inheritance chain. See
<a class="reference internal" href="inheritance.html">Inheritance</a>.
</div>
</div>
<div class="section" id="inheritable-namespaces">
<h2>Inheritable Namespaces<a class="headerlink" href="#inheritable-namespaces" title="Permalink to this headline">¶</a></h2>
The <code class="docutils literal notranslate">&lt;%namespace&gt;</code> tag includes an optional attribute
<code class="docutils literal notranslate">inheritable=&quot;True&quot;</code>, which will cause the namespace to be
attached to the <code class="docutils literal notranslate">self</code> namespace. Since <code class="docutils literal notranslate">self</code> is globally
available throughout an inheritance chain (described in the next
section), all the templates in an inheritance chain can get at
the namespace imported in a super-template via <code class="docutils literal notranslate">self</code>.
<div class="highlight-mako notranslate"><div class="highlight"><pre>## base.html
&lt;%namespace name=&quot;foo&quot; file=&quot;foo.html&quot; inheritable=&quot;True&quot;/&gt;

${next.body()}

## somefile.html
&lt;%inherit file=&quot;base.html&quot;/&gt;

${self.foo.bar()}</pre></div>
</div>
This allows a super-template to load a whole bunch of namespaces
that its inheriting templates can get to, without them having to
explicitly load those namespaces themselves.
The <code class="docutils literal notranslate">import=&quot;*&quot;</code> part of the <code class="docutils literal notranslate">&lt;%namespace&gt;</code> tag doesn’t yet
interact with the <code class="docutils literal notranslate">inheritable</code> flag, so currently you have to
use the explicit namespace name off of <code class="docutils literal notranslate">self</code>, followed by the
desired function name. But more on this in a future release.
</div>
<div class="section" id="namespace-api-usage-example-static-dependencies">
<h2>Namespace API Usage Example - Static Dependencies<a class="headerlink" href="#namespace-api-usage-example-static-dependencies" title="Permalink to this headline">¶</a></h2>
The <code class="docutils literal notranslate">&lt;%namespace&gt;</code> tag at runtime produces an instance of
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>. Programmatic access of <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> can be used
to build various kinds of scaffolding in templates and between templates.
A common request is the ability for a particular template to declare
“static includes” - meaning, the usage of a particular set of defs requires
that certain Javascript/CSS files are present. Using <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> as the
object that holds together the various templates present, we can build a variety
of such schemes. In particular, the <a class="reference internal" href="runtime.html#mako.runtime.Context" title="mako.runtime.Context"><code class="xref py py-class docutils literal notranslate">Context</code></a> has a <code class="docutils literal notranslate">namespaces</code>
attribute, which is a dictionary of all <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> objects declared.
Iterating the values of this dictionary will provide a <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>
object for each time the <code class="docutils literal notranslate">&lt;%namespace&gt;</code> tag was used, anywhere within the
inheritance chain.
<div class="section" id="version-one-use-namespace-attr">
<h3>Version One - Use <a class="reference internal" href="#mako.runtime.Namespace.attr" title="mako.runtime.Namespace.attr"><code class="xref py py-attr docutils literal notranslate">Namespace.attr</code></a><a class="headerlink" href="#version-one-use-namespace-attr" title="Permalink to this headline">¶</a></h3>
The <a class="reference internal" href="#mako.runtime.Namespace.attr" title="mako.runtime.Namespace.attr"><code class="xref py py-attr docutils literal notranslate">Namespace.attr</code></a> attribute allows us to locate any variables declared
in the <code class="docutils literal notranslate">&lt;%! %&gt;</code> of a template.
<div class="highlight-mako notranslate"><div class="highlight"><pre>## base.mako
## base-most template, renders layout etc.
&lt;html&gt;
&lt;head&gt;
## traverse through all namespaces present,
## look for an attribute named &#39;includes&#39;
% for ns in context.namespaces.values():
 % for incl in getattr(ns.attr, &#39;includes&#39;, []):
 ${incl}
 % endfor
% endfor
&lt;/head&gt;
&lt;body&gt;
${next.body()}
&lt;/body
&lt;/html&gt;

## library.mako
## library functions.
&lt;%!
 includes = [
 &#39;&lt;link rel=&quot;stylesheet&quot; type=&quot;text/css&quot; href=&quot;mystyle.css&quot;/&gt;&#39;,
 &#39;&lt;script type=&quot;text/javascript&quot; src=&quot;functions.js&quot;&gt;&lt;/script&gt;&#39;
 ]
%&gt;

&lt;%def name=&quot;mytag()&quot;&gt;
 &lt;form&gt;
 ${caller.body()}
 &lt;/form&gt;
&lt;/%def&gt;

## index.mako
## calling template.
&lt;%inherit file=&quot;base.mako&quot;/&gt;
&lt;%namespace name=&quot;foo&quot; file=&quot;library.mako&quot;/&gt;

&lt;%foo:mytag&gt;
 a form
&lt;/%foo:mytag&gt;</pre></div>
</div>
Above, the file <code class="docutils literal notranslate">library.mako</code> declares an attribute <code class="docutils literal notranslate">includes</code> inside its global <code class="docutils literal notranslate">&lt;%! %&gt;</code> section.
<code class="docutils literal notranslate">index.mako</code> includes this template using the <code class="docutils literal notranslate">&lt;%namespace&gt;</code> tag. The base template <code class="docutils literal notranslate">base.mako</code>, which is the inherited parent of <code class="docutils literal notranslate">index.mako</code> and is responsible for layout, then locates this attribute and iterates through its contents to produce the includes that are specific to <code class="docutils literal notranslate">library.mako</code>.
</div>
<div class="section" id="version-two-use-a-specific-named-def">
<h3>Version Two - Use a specific named def<a class="headerlink" href="#version-two-use-a-specific-named-def" title="Permalink to this headline">¶</a></h3>
In this version, we put the includes into a <code class="docutils literal notranslate">&lt;%def&gt;</code> that
follows a naming convention.
<div class="highlight-mako notranslate"><div class="highlight"><pre>## base.mako
## base-most template, renders layout etc.
&lt;html&gt;
&lt;head&gt;
## traverse through all namespaces present,
## look for a %def named &#39;includes&#39;
% for ns in context.namespaces.values():
 % if hasattr(ns, &#39;includes&#39;):
 ${ns.includes()}
 % endif
% endfor
&lt;/head&gt;
&lt;body&gt;
${next.body()}
&lt;/body
&lt;/html&gt;

## library.mako
## library functions.

&lt;%def name=&quot;includes()&quot;&gt;
 &lt;link rel=&quot;stylesheet&quot; type=&quot;text/css&quot; href=&quot;mystyle.css&quot;/&gt;
 &lt;script type=&quot;text/javascript&quot; src=&quot;functions.js&quot;&gt;&lt;/script&gt;
&lt;/%def&gt;

&lt;%foo:mytag&gt;
 a form
&lt;/%foo:mytag&gt;</pre></div>
</div>
In this version, <code class="docutils literal notranslate">library.mako</code> declares a <code class="docutils literal notranslate">&lt;%def&gt;</code> named <code class="docutils literal notranslate">includes</code>. The example works
identically to the previous one, except that <code class="docutils literal notranslate">base.mako</code> looks for defs named <code class="docutils literal notranslate">include</code>
on each namespace it examines.
</div>
</div>
<div class="section" id="api-reference">
<h2>API Reference<a class="headerlink" href="#api-reference" title="Permalink to this headline">¶</a></h2>
<dl class="class">
<dt id="mako.runtime.Namespace">
class <code class="sig-prename descclassname">mako.runtime.</code><code class="sig-name descname">Namespace</code>(name, context, callables=None, inherits=None, populate_self=True, calling_uri=None)<a class="headerlink" href="#mako.runtime.Namespace" title="Permalink to this definition">¶</a></dt>
<dd>Bases: <code class="xref py py-class docutils literal notranslate">object</code>
Provides access to collections of rendering methods, which
can be local, from other templates, or from imported modules.
To access a particular rendering method referenced by a
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>, use plain attribute access:
<div class="highlight-mako notranslate"><div class="highlight"><pre>${some_namespace.foo(x, y, z)}</pre></div>
</div>
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> also contains several built-in attributes
described here.
<dl class="attribute">
<dt id="mako.runtime.Namespace.attr">
<code class="sig-name descname">attr</code><a class="headerlink" href="#mako.runtime.Namespace.attr" title="Permalink to this definition">¶</a></dt>
<dd>Access module level attributes by name.
This accessor allows templates to supply “scalar”
attributes which are particularly handy in inheritance
relationships.
<div class="admonition seealso">
See also
<a class="reference internal" href="inheritance.html#inheritance-attr">Inheritable Attributes</a>
<a class="reference internal" href="#namespace-attr-for-includes">Version One - Use Namespace.attr</a>
</div>
</dd></dl>

<dl class="method">
<dt id="mako.runtime.Namespace.cache">
property <code class="sig-name descname">cache</code><a class="headerlink" href="#mako.runtime.Namespace.cache" title="Permalink to this definition">¶</a></dt>
<dd>Return the <a class="reference internal" href="caching.html#mako.cache.Cache" title="mako.cache.Cache"><code class="xref py py-class docutils literal notranslate">Cache</code></a> object referenced
by this <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> object’s
<a class="reference internal" href="usage.html#mako.template.Template" title="mako.template.Template"><code class="xref py py-class docutils literal notranslate">Template</code></a>.
</dd></dl>

<dl class="attribute">
<dt id="mako.runtime.Namespace.context">
<code class="sig-name descname">context</code> = None<a class="headerlink" href="#mako.runtime.Namespace.context" title="Permalink to this definition">¶</a></dt>
<dd>The <a class="reference internal" href="runtime.html#mako.runtime.Context" title="mako.runtime.Context"><code class="xref py py-class docutils literal notranslate">Context</code></a> object for this <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>.
Namespaces are often created with copies of contexts that
contain slightly different data, particularly in inheritance
scenarios. Using the <a class="reference internal" href="runtime.html#mako.runtime.Context" title="mako.runtime.Context"><code class="xref py py-class docutils literal notranslate">Context</code></a> off of a <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> one
can traverse an entire chain of templates that inherit from
one-another.
</dd></dl>

<dl class="attribute">
<dt id="mako.runtime.Namespace.filename">
<code class="sig-name descname">filename</code> = None<a class="headerlink" href="#mako.runtime.Namespace.filename" title="Permalink to this definition">¶</a></dt>
<dd>The path of the filesystem file used for this
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>’s module or template.
If this is a pure module-based
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>, this evaluates to <code class="docutils literal notranslate">module.__file__</code>. If a
template-based namespace, it evaluates to the original
template file location.
</dd></dl>

<dl class="method">
<dt id="mako.runtime.Namespace.get_cached">
<code class="sig-name descname">get_cached</code>(key, **kwargs)<a class="headerlink" href="#mako.runtime.Namespace.get_cached" title="Permalink to this definition">¶</a></dt>
<dd>Return a value from the <a class="reference internal" href="caching.html#mako.cache.Cache" title="mako.cache.Cache"><code class="xref py py-class docutils literal notranslate">Cache</code></a> referenced by this
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> object’s <a class="reference internal" href="usage.html#mako.template.Template" title="mako.template.Template"><code class="xref py py-class docutils literal notranslate">Template</code></a>.
The advantage to this method versus direct access to the
<a class="reference internal" href="caching.html#mako.cache.Cache" title="mako.cache.Cache"><code class="xref py py-class docutils literal notranslate">Cache</code></a> is that the configuration parameters
declared in <code class="docutils literal notranslate">&lt;%page&gt;</code> take effect here, thereby calling
up the same configured backend as that configured
by <code class="docutils literal notranslate">&lt;%page&gt;</code>.
</dd></dl>

<dl class="method">
<dt id="mako.runtime.Namespace.get_namespace">
<code class="sig-name descname">get_namespace</code>(uri)<a class="headerlink" href="#mako.runtime.Namespace.get_namespace" title="Permalink to this definition">¶</a></dt>
<dd>Return a <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> corresponding to the given <code class="docutils literal notranslate">uri</code>.
If the given <code class="docutils literal notranslate">uri</code> is a relative URI (i.e. it does not
contain a leading slash <code class="docutils literal notranslate">/</code>), the <code class="docutils literal notranslate">uri</code> is adjusted to
be relative to the <code class="docutils literal notranslate">uri</code> of the namespace itself. This
method is therefore mostly useful off of the built-in
<code class="docutils literal notranslate">local</code> namespace, described in <a class="reference internal" href="#namespace-local">local</a>.
In
most cases, a template wouldn’t need this function, and
should instead use the <code class="docutils literal notranslate">&lt;%namespace&gt;</code> tag to load
namespaces. However, since all <code class="docutils literal notranslate">&lt;%namespace&gt;</code> tags are
evaluated before the body of a template ever runs,
this method can be used to locate namespaces using
expressions that were generated within the body code of
the template, or to conditionally use a particular
namespace.
</dd></dl>

<dl class="method">
<dt id="mako.runtime.Namespace.get_template">
<code class="sig-name descname">get_template</code>(uri)<a class="headerlink" href="#mako.runtime.Namespace.get_template" title="Permalink to this definition">¶</a></dt>
<dd>Return a <a class="reference internal" href="usage.html#mako.template.Template" title="mako.template.Template"><code class="xref py py-class docutils literal notranslate">Template</code></a> from the given <code class="docutils literal notranslate">uri</code>.
The <code class="docutils literal notranslate">uri</code> resolution is relative to the <code class="docutils literal notranslate">uri</code> of this
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> object’s <a class="reference internal" href="usage.html#mako.template.Template" title="mako.template.Template"><code class="xref py py-class docutils literal notranslate">Template</code></a>.
</dd></dl>

<dl class="method">
<dt id="mako.runtime.Namespace.include_file">
<code class="sig-name descname">include_file</code>(uri, **kwargs)<a class="headerlink" href="#mako.runtime.Namespace.include_file" title="Permalink to this definition">¶</a></dt>
<dd>Include a file at the given <code class="docutils literal notranslate">uri</code>.
</dd></dl>

<dl class="attribute">
<dt id="mako.runtime.Namespace.module">
<code class="sig-name descname">module</code> = None<a class="headerlink" href="#mako.runtime.Namespace.module" title="Permalink to this definition">¶</a></dt>
<dd>The Python module referenced by this <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>.
If the namespace references a <a class="reference internal" href="usage.html#mako.template.Template" title="mako.template.Template"><code class="xref py py-class docutils literal notranslate">Template</code></a>, then
this module is the equivalent of <code class="docutils literal notranslate">template.module</code>,
i.e. the generated module for the template.
</dd></dl>

<dl class="attribute">
<dt id="mako.runtime.Namespace.template">
<code class="sig-name descname">template</code> = None<a class="headerlink" href="#mako.runtime.Namespace.template" title="Permalink to this definition">¶</a></dt>
<dd>The <a class="reference internal" href="usage.html#mako.template.Template" title="mako.template.Template"><code class="xref py py-class docutils literal notranslate">Template</code></a> object referenced by this
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>, if any.
</dd></dl>

<dl class="attribute">
<dt id="mako.runtime.Namespace.uri">
<code class="sig-name descname">uri</code> = None<a class="headerlink" href="#mako.runtime.Namespace.uri" title="Permalink to this definition">¶</a></dt>
<dd>The URI for this <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>’s template.
I.e. whatever was sent to <a class="reference internal" href="usage.html#mako.lookup.TemplateLookup.get_template" title="mako.lookup.TemplateLookup.get_template"><code class="xref py py-meth docutils literal notranslate">TemplateLookup.get_template()</code></a>.
This is the equivalent of <code class="xref py py-attr docutils literal notranslate">Template.uri</code>.
</dd></dl>

</dd></dl>

<dl class="class">
<dt id="mako.runtime.TemplateNamespace">
class <code class="sig-prename descclassname">mako.runtime.</code><code class="sig-name descname">TemplateNamespace</code>(name, context, template=None, templateuri=None, callables=None, inherits=None, populate_self=True, calling_uri=None)<a class="headerlink" href="#mako.runtime.TemplateNamespace" title="Permalink to this definition">¶</a></dt>
<dd>Bases: <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">mako.runtime.Namespace</code></a>
Bases: <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">mako.runtime.Namespace</code></a>
A <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> specific to a <a class="reference internal" href="usage.html#mako.template.Template" title="mako.template.Template"><code class="xref py py-class docutils literal notranslate">Template</code></a> instance.
<dl class="method">
<dt id="mako.runtime.TemplateNamespace.filename">
property <code class="sig-name descname">filename</code><a class="headerlink" href="#mako.runtime.TemplateNamespace.filename" title="Permalink to this definition">¶</a></dt>
<dd>The path of the filesystem file used for this
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>’s module or template.
</dd></dl>

<dl class="method">
<dt id="mako.runtime.TemplateNamespace.module">
property <code class="sig-name descname">module</code><a class="headerlink" href="#mako.runtime.TemplateNamespace.module" title="Permalink to this definition">¶</a></dt>
<dd>The Python module referenced by this <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>.
If the namespace references a <a class="reference internal" href="usage.html#mako.template.Template" title="mako.template.Template"><code class="xref py py-class docutils literal notranslate">Template</code></a>, then
this module is the equivalent of <code class="docutils literal notranslate">template.module</code>,
i.e. the generated module for the template.
</dd></dl>

<dl class="method">
<dt id="mako.runtime.TemplateNamespace.uri">
property <code class="sig-name descname">uri</code><a class="headerlink" href="#mako.runtime.TemplateNamespace.uri" title="Permalink to this definition">¶</a></dt>
<dd>The URI for this <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>’s template.
I.e. whatever was sent to <a class="reference internal" href="usage.html#mako.lookup.TemplateLookup.get_template" title="mako.lookup.TemplateLookup.get_template"><code class="xref py py-meth docutils literal notranslate">TemplateLookup.get_template()</code></a>.
This is the equivalent of <code class="xref py py-attr docutils literal notranslate">Template.uri</code>.
</dd></dl>

</dd></dl>

<dl class="class">
<dt id="mako.runtime.ModuleNamespace">
class <code class="sig-prename descclassname">mako.runtime.</code><code class="sig-name descname">ModuleNamespace</code>(name, context, module, callables=None, inherits=None, populate_self=True, calling_uri=None)<a class="headerlink" href="#mako.runtime.ModuleNamespace" title="Permalink to this definition">¶</a></dt>
<dd>Bases: <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">mako.runtime.Namespace</code></a>
Bases: <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">mako.runtime.Namespace</code></a>
A <a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a> specific to a Python module instance.
<dl class="method">
<dt id="mako.runtime.ModuleNamespace.filename">
property <code class="sig-name descname">filename</code><a class="headerlink" href="#mako.runtime.ModuleNamespace.filename" title="Permalink to this definition">¶</a></dt>
<dd>The path of the filesystem file used for this
<a class="reference internal" href="#mako.runtime.Namespace" title="mako.runtime.Namespace"><code class="xref py py-class docutils literal notranslate">Namespace</code></a>’s module or template.
</dd></dl>

</dd></dl>

<dl class="function">
<dt id="mako.runtime.supports_caller">
<code class="sig-prename descclassname">mako.runtime.</code><code class="sig-name descname">supports_caller</code>(func)<a class="headerlink" href="#mako.runtime.supports_caller" title="Permalink to this definition">¶</a></dt>
<dd>Apply a caller_stack compatibility decorator to a plain
Python function.
See the example in <a class="reference internal" href="#namespaces-python-modules">Namespaces from Regular Python Modules</a>.
</dd></dl>

<dl class="function">
<dt id="mako.runtime.capture">
<code class="sig-prename descclassname">mako.runtime.</code><code class="sig-name descname">capture</code>(context, callable_, *args, **kwargs)<a class="headerlink" href="#mako.runtime.capture" title="Permalink to this definition">¶</a></dt>
<dd>Execute the given template def, capturing the output into
a buffer.
See the example in <a class="reference internal" href="#namespaces-python-modules">Namespaces from Regular Python Modules</a>.
</dd></dl>

</div>
</div>

</div>

<div id="docs-bottom-navigation" class="docs-navigation-links">
 Previous:
 <a href="runtime.html" title="previous chapter">The Mako Runtime Environment</a>
 Next:
 <a href="inheritance.html" title="next chapter">Inheritance</a>

<div id="docs-copyright">
 &copy; Copyright the Mako authors and contributors.
 Documentation generated using <a href="http://sphinx.pocoo.org/">Sphinx</a> 2.1.2
 with Mako templates.
 </div>
</div>

</div>

<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/language_data.js"></script>

</body>
</html>