/usr/lib64/python2.6/site-packages/jinja2
Edit: /usr/lib64/python2.6/site-packages/jinja2/ext.pyo (17614B)
Ñò
{ÉyJc
@ s? d Z d d k l Z d d k l Z d d k Td d k l Z d d k l Z l
Z
d d k l Z l
Z
d d k l Z l Z l Z l Z d Z d e f d
„ ƒ YZ d e f d „ ƒ YZ e d „ ƒ Z d e f d „ ƒ YZ d e f d „ ƒ YZ d e f d „ ƒ YZ e e d „ Z d „ Z e Z e Z e Z! d S( s
jinja2.ext
~~~~~~~~~~
Jinja extensions allow to add custom tags similar to the way django custom
tags work. By default two example extensions exist: an i18n and a cache
extension.
:copyright: (c) 2009 by the Jinja Team.
:license: BSD.
iÿÿÿÿ( t deque( t nodes( t *( t get_spontaneous_environment( t Undefinedt concat( t TemplateAssertionErrort TemplateSyntaxError( t contextfunctiont
import_stringt Markupt nextt _t gettextt ngettextt ExtensionRegistryc B s e Z d Z d „ Z RS( s) Gives the extension an unique identifier.c C s3 t i | | | | ƒ } | i d | i | _ | S( Nt .( t typet __new__t
__module__t __name__t
identifier( t clst namet basest dt rv( ( s0 /usr/lib64/python2.6/site-packages/jinja2/ext.pyR s ( R R t __doc__R ( ( ( s0 /usr/lib64/python2.6/site-packages/jinja2/ext.pyR s t Extensionc B sq e Z d Z e Z e ƒ Z d „ Z d „ Z d d „ Z
d „ Z d „ Z d d „ Z
d d d d d d „ Z RS( sg Extensions can be used to add extra functionality to the Jinja template
system at the parser level. Custom extensions are bound to an environment
but may not store environment specific data on `self`. The reason for
this is that an extension can be bound to another environment (for
overlays) by creating a copy and reassigning the `environment` attribute.
As extensions are created by the environment they cannot accept any
arguments for configuration. One may want to work around that by using
a factory function, but that is not possible as extensions are identified
by their import name. The correct way to configure the extension is
storing the configuration values on the environment. Because this way the
environment ends up acting as central configuration storage the
attributes may clash which is why extensions have to ensure that the names
they choose for configuration are not too generic. ``prefix`` for example
is a terrible name, ``fragment_cache_prefix`` on the other hand is a good
name as includes the name of the extension (fragment cache).
c C s
| | _ d S( N( t environment( t selfR ( ( s0 /usr/lib64/python2.6/site-packages/jinja2/ext.pyt __init__<