diff options
Diffstat (limited to 'doc/build')
| -rw-r--r-- | doc/build/caching.rst | 6 | ||||
| -rw-r--r-- | doc/build/namespaces.rst | 42 |
2 files changed, 6 insertions, 42 deletions
diff --git a/doc/build/caching.rst b/doc/build/caching.rst index 3ad35ff..0620d32 100644 --- a/doc/build/caching.rst +++ b/doc/build/caching.rst @@ -119,3 +119,9 @@ sections programmatically: # invalidate an arbitrary key template.cache.invalidate('somekey') +API Reference +============== + +.. autoclass:: mako.cache.Cache + :members: + :show-inheritance:
\ No newline at end of file diff --git a/doc/build/namespaces.rst b/doc/build/namespaces.rst index 5939020..0da3488 100644 --- a/doc/build/namespaces.rst +++ b/doc/build/namespaces.rst @@ -334,48 +334,6 @@ API Reference .. autoclass:: mako.runtime.Namespace :show-inheritance: :members: - - .. py:attribute:: attr - - allows access module level attributes by name. This - accessor allows templates to supply "scalar" attributes which - are particularly handy in inheritance relationships. See the - example in :ref:`inheritance_toplevel`. - - .. py:attribute:: module - - the Python module referenced by this Namespace. - If the namespace references a :class:`.Template`, then this module - is the equivalent of ``template.module``, i.e. the generated - module for the template. - - .. py:attribute:: filename - - the path of the filesystem file used for this - Namespace's module or template. If this is a pure module-based - Namespace, this evaluates to ``module.__file__``. If a - template-based namespace, it evaluates to the original - template file location. - - .. py:attribute:: template - - the :class:`.Template` object referenced by this - :class:`.Namespace`, if any. - - .. py:attribute:: uri - - the uri for this Namespace's template (i.e. whatever - was sent to :meth:`.TemplateLookup.get_template()`). This is the equivalent - of :attr:`Template.uri`. - - .. py:attribute:: context - - The :class:`.Context` object for this namespace. - Namespaces are often created with copies of contexts that - contain slightly different data, particularly in inheritance - scenarios. Using the :class:`.Context` off of a :class:`.Namespace` one - can traverse an entire chain of templates that inherit from - one-another. .. autofunction:: mako.runtime.supports_caller |