5 :synopsis: public Jinja2 API
7 This document describes the API to Jinja2 and not the template language. It
8 will be most useful as reference to those implementing the template interface
9 to the application and not those who are creating Jinja2 templates.
14 Jinja2 uses a central object called the template :class:`Environment`.
15 Instances of this class are used to store the configuration, global objects
16 and are used to load templates from the file system or other locations.
17 Even if you are creating templates from strings by using the constructor of
18 :class:`Template` class, an environment is created automatically for you,
21 Most applications will create one :class:`Environment` object on application
22 initialization and use that to load templates. In some cases it's however
23 useful to have multiple environments side by side, if different configurations
26 The simplest way to configure Jinja2 to load templates for your application
27 looks roughly like this::
29 from jinja2 import Environment, PackageLoader
30 env = Environment(loader=PackageLoader('yourapplication', 'templates'))
32 This will create a template environment with the default settings and a
33 loader that looks up the templates in the `templates` folder inside the
34 `yourapplication` python package. Different loaders are available
35 and you can also write your own if you want to load templates from a
36 database or other resources.
38 To load a template from this environment you just have to call the
39 :meth:`get_template` method which then returns the loaded :class:`Template`::
41 template = env.get_template('mytemplate.html')
43 To render it with some variables, just call the :meth:`render` method::
45 print template.render(the='variables', go='here')
47 Using a template loader rather then passing strings to :class:`Template`
48 or :meth:`Environment.from_string` has multiple advantages. Besides being
49 a lot easier to use it also enables template inheritance.
55 Jinja2 is using unicode internally which means that you have to pass unicode
56 objects to the render function or bytestrings that only consist of ASCII
57 characters. Additionally newlines are normalized to one end of line
58 sequence which is per default UNIX style (``\n``).
60 Python 2.x supports two ways of representing string objects. One is the
61 `str` type and the other is the `unicode` type, both of which extend a type
62 called `basestring`. Unfortunately the default is `str` which should not
63 be used to store text based information unless only ASCII characters are
64 used. With Python 2.6 it is possible to make `unicode` the default on a per
65 module level and with Python 3 it will be the default.
67 To explicitly use a unicode string you have to prefix the string literal
68 with a `u`: ``u'Hänsel und Gretel sagen Hallo'``. That way Python will
69 store the string as unicode by decoding the string with the character
70 encoding from the current Python module. If no encoding is specified this
71 defaults to 'ASCII' which means that you can't use any non ASCII identifier.
73 To set a better module encoding add the following comment to the first or
74 second line of the Python module using the unicode literal::
76 # -*- coding: utf-8 -*-
78 We recommend utf-8 as Encoding for Python modules and templates as it's
79 possible to represent every Unicode character in utf-8 and because it's
80 backwards compatible to ASCII. For Jinja2 the default encoding of templates
81 is assumed to be utf-8.
83 It is not possible to use Jinja2 to process non unicode data. The reason
84 for this is that Jinja2 uses Unicode already on the language level. For
85 example Jinja2 treats the non-breaking space as valid whitespace inside
86 expressions which requires knowledge of the encoding or operating on an
89 For more details about unicode in Python have a look at the excellent
90 `Unicode documentation`_.
92 Another important thing is how Jinja2 is handling string literals in
93 templates. A naive implementation would be using unicode strings for
94 all string literals but it turned out in the past that this is problematic
95 as some libraries are typechecking against `str` explicitly. For example
96 `datetime.strftime` does not accept unicode arguments. To not break it
97 completely Jinja2 is returning `str` for strings that fit into ASCII and
98 for everything else `unicode`:
100 >>> m = Template(u"{% set a, b = 'foo', 'föö' %}").module
107 .. _Unicode documentation: http://docs.python.org/dev/howto/unicode.html
112 The high-level API is the API you will use in the application to load and
113 render Jinja2 templates. The :ref:`low-level-api` on the other side is only
114 useful if you want to dig deeper into Jinja2 or :ref:`develop extensions
117 .. autoclass:: Environment([options])
118 :members: from_string, get_template, join_path, extend, compile_expression
120 .. attribute:: shared
122 If a template was created by using the :class:`Template` constructor
123 an environment is created automatically. These environments are
124 created as shared environments which means that multiple templates
125 may have the same anonymous environment. For all shared environments
126 this attribute is `True`, else `False`.
128 .. attribute:: sandboxed
130 If the environment is sandboxed this attribute is `True`. For the
131 sandbox mode have a look at the documentation for the
132 :class:`~jinja2.sandbox.SandboxedEnvironment`.
134 .. attribute:: filters
136 A dict of filters for this environment. As long as no template was
137 loaded it's safe to add new filters or remove old. For custom filters
138 see :ref:`writing-filters`. For valid filter names have a look at
139 :ref:`identifier-naming`.
143 A dict of test functions for this environment. As long as no
144 template was loaded it's safe to modify this dict. For custom tests
145 see :ref:`writing-tests`. For valid test names have a look at
146 :ref:`identifier-naming`.
148 .. attribute:: globals
150 A dict of global variables. These variables are always available
151 in a template. As long as no template was loaded it's safe
152 to modify this dict. For more details see :ref:`global-namespace`.
153 For valid object names have a look at :ref:`identifier-naming`.
155 .. automethod:: overlay([options])
157 .. method:: undefined([hint, obj, name, exc])
159 Creates a new :class:`Undefined` object for `name`. This is useful
160 for filters or functions that may return undefined objects for
161 some operations. All parameters except of `hint` should be provided
162 as keyword parameters for better readability. The `hint` is used as
163 error message for the exception if provided, otherwise the error
164 message will be generated from `obj` and `name` automatically. The exception
165 provided as `exc` is raised if something with the generated undefined
166 object is done that the undefined object does not allow. The default
167 exception is :exc:`UndefinedError`. If a `hint` is provided the
168 `name` may be ommited.
170 The most common way to create an undefined object is by providing
173 return environment.undefined(name='some_name')
175 This means that the name `some_name` is not defined. If the name
176 was from an attribute of an object it makes sense to tell the
177 undefined object the holder object to improve the error message::
179 if not hasattr(obj, 'attr'):
180 return environment.undefined(obj=obj, name='attr')
182 For a more complex example you can provide a hint. For example
183 the :func:`first` filter creates an undefined object that way::
185 return environment.undefined('no first item, sequence was empty')
187 If it the `name` or `obj` is known (for example because an attribute
188 was accessed) it shold be passed to the undefined object, even if
189 a custom `hint` is provided. This gives undefined objects the
190 possibility to enhance the error message.
192 .. autoclass:: Template
193 :members: module, make_module
195 .. attribute:: globals
197 The dict with the globals of that template. It's unsafe to modify
198 this dict as it may be shared with other templates or the environment
199 that loaded the template.
203 The loading name of the template. If the template was loaded from a
204 string this is `None`.
206 .. attribute:: filename
208 The filename of the template on the file system if it was loaded from
209 there. Otherwise this is `None`.
211 .. automethod:: render([context])
213 .. automethod:: generate([context])
215 .. automethod:: stream([context])
218 .. autoclass:: jinja2.environment.TemplateStream()
219 :members: disable_buffering, enable_buffering, dump
222 .. _identifier-naming:
227 Jinja2 uses the regular Python 2.x naming rules. Valid identifiers have to
228 match ``[a-zA-Z_][a-zA-Z0-9_]*``. As a matter of fact non ASCII characters
229 are currently not allowed. This limitation will probably go away as soon as
230 unicode identifiers are fully specified for Python 3.
232 Filters and tests are looked up in separate namespaces and have slightly
233 modified identifier syntax. Filters and tests may contain dots to group
234 filters and tests by topic. For example it's perfectly valid to add a
235 function into the filter dict and call it `to.unicode`. The regular
236 expression for filter and test identifiers is
237 ``[a-zA-Z_][a-zA-Z0-9_]*(\.[a-zA-Z_][a-zA-Z0-9_]*)*```.
243 These classes can be used as undefined types. The :class:`Environment`
244 constructor takes an `undefined` parameter that can be one of those classes
245 or a custom subclass of :class:`Undefined`. Whenever the template engine is
246 unable to look up a name or access an attribute one of those objects is
247 created and returned. Some operations on undefined values are then allowed,
250 The closest to regular Python behavior is the `StrictUndefined` which
251 disallows all operations beside testing if it's an undefined object.
253 .. autoclass:: jinja2.Undefined()
255 .. attribute:: _undefined_hint
257 Either `None` or an unicode string with the error message for
258 the undefined object.
260 .. attribute:: _undefined_obj
262 Either `None` or the owner object that caused the undefined object
263 to be created (for example because an attribute does not exist).
265 .. attribute:: _undefined_name
267 The name for the undefined variable / attribute or just `None`
268 if no such information exists.
270 .. attribute:: _undefined_exception
272 The exception that the undefined object wants to raise. This
273 is usually one of :exc:`UndefinedError` or :exc:`SecurityError`.
275 .. method:: _fail_with_undefined_error(\*args, \**kwargs)
277 When called with any arguments this method raises
278 :attr:`_undefined_exception` with an error message generated
279 from the undefined hints stored on the undefined object.
281 .. autoclass:: jinja2.DebugUndefined()
283 .. autoclass:: jinja2.StrictUndefined()
285 Undefined objects are created by calling :attr:`undefined`.
287 .. admonition:: Implementation
289 :class:`Undefined` objects are implemented by overriding the special
290 `__underscore__` methods. For example the default :class:`Undefined`
291 class implements `__unicode__` in a way that it returns an empty
292 string, however `__int__` and others still fail with an exception. To
293 allow conversion to int by returning ``0`` you can implement your own::
295 class NullUndefined(Undefined):
301 To disallow a method, just override it and raise
302 :attr:`~Undefined._undefined_exception`. Because this is a very common
303 idom in undefined objects there is the helper method
304 :meth:`~Undefined._fail_with_undefined_error` that does the error raising
305 automatically. Here a class that works like the regular :class:`Undefined`
306 but chokes on iteration::
308 class NonIterableUndefined(Undefined):
309 __iter__ = Undefined._fail_with_undefined_error
315 .. autoclass:: jinja2.runtime.Context()
316 :members: resolve, get_exported, get_all
318 .. attribute:: parent
320 A dict of read only, global variables the template looks up. These
321 can either come from another :class:`Context`, from the
322 :attr:`Environment.globals` or :attr:`Template.globals` or points
323 to a dict created by combining the globals with the variables
324 passed to the render function. It must not be altered.
328 The template local variables. This list contains environment and
329 context functions from the :attr:`parent` scope as well as local
330 modifications and exported variables from the template. The template
331 will modify this dict during template evaluation but filters and
332 context functions are not allowed to modify it.
334 .. attribute:: environment
336 The environment that loaded the template.
338 .. attribute:: exported_vars
340 This set contains all the names the template exports. The values for
341 the names are in the :attr:`vars` dict. In order to get a copy of the
342 exported variables as dict, :meth:`get_exported` can be used.
346 The load name of the template owning this context.
348 .. attribute:: blocks
350 A dict with the current mapping of blocks in the template. The keys
351 in this dict are the names of the blocks, and the values a list of
352 blocks registered. The last item in each list is the current active
353 block (latest in the inheritance chain).
355 .. automethod:: jinja2.runtime.Context.call(callable, \*args, \**kwargs)
358 .. admonition:: Implementation
360 Context is immutable for the same reason Python's frame locals are
361 immutable inside functions. Both Jinja2 and Python are not using the
362 context / frame locals as data storage for variables but only as primary
365 When a template accesses a variable the template does not define, Jinja2
366 looks up the variable in the context, after that the variable is treated
367 as if it was defined in the template.
375 Loaders are responsible for loading templates from a resource such as the
376 file system. The environment will keep the compiled modules in memory like
377 Python's `sys.modules`. Unlike `sys.modules` however this cache is limited in
378 size by default and templates are automatically reloaded.
379 All loaders are subclasses of :class:`BaseLoader`. If you want to create your
380 own loader, subclass :class:`BaseLoader` and override `get_source`.
382 .. autoclass:: jinja2.BaseLoader
383 :members: get_source, load
385 Here a list of the builtin loaders Jinja2 provides:
387 .. autoclass:: jinja2.FileSystemLoader
389 .. autoclass:: jinja2.PackageLoader
391 .. autoclass:: jinja2.DictLoader
393 .. autoclass:: jinja2.FunctionLoader
395 .. autoclass:: jinja2.PrefixLoader
397 .. autoclass:: jinja2.ChoiceLoader
405 Jinja 2.1 and higher support external bytecode caching. Bytecode caches make
406 it possible to store the generated bytecode on the file system or a different
407 location to avoid parsing the templates on first use.
409 This is especially useful if you have a web application that is initialized on
410 the first request and Jinja compiles many templates at once which slows down
413 To use a bytecode cache, instanciate it and pass it to the :class:`Environment`.
415 .. autoclass:: jinja2.BytecodeCache
416 :members: load_bytecode, dump_bytecode, clear
418 .. autoclass:: jinja2.bccache.Bucket
419 :members: write_bytecode, load_bytecode, bytecode_from_string,
420 bytecode_to_string, reset
422 .. attribute:: environment
424 The :class:`Environment` that created the bucket.
428 The unique cache key for this bucket
432 The bytecode if it's loaded, otherwise `None`.
435 Builtin bytecode caches:
437 .. autoclass:: jinja2.FileSystemBytecodeCache
439 .. autoclass:: jinja2.MemcachedBytecodeCache
445 These helper functions and classes are useful if you add custom filters or
446 functions to a Jinja2 environment.
448 .. autofunction:: jinja2.environmentfilter
450 .. autofunction:: jinja2.contextfilter
452 .. autofunction:: jinja2.environmentfunction
454 .. autofunction:: jinja2.contextfunction
456 .. function:: escape(s)
458 Convert the characters ``&``, ``<``, ``>``, ``'``, and ``"`` in string `s`
459 to HTML-safe sequences. Use this if you need to display text that might
460 contain such characters in HTML. This function will not escaped objects
461 that do have an HTML representation such as already escaped data.
463 The return value is a :class:`Markup` string.
465 .. autofunction:: jinja2.clear_caches
467 .. autofunction:: jinja2.is_undefined
469 .. autoclass:: jinja2.Markup([string])
470 :members: escape, unescape, striptags
474 The Jinja2 :class:`Markup` class is compatible with at least Pylons and
475 Genshi. It's expected that more template engines and framework will pick
476 up the `__html__` concept soon.
482 .. autoexception:: jinja2.TemplateError
484 .. autoexception:: jinja2.UndefinedError
486 .. autoexception:: jinja2.TemplateNotFound
488 .. autoexception:: jinja2.TemplateSyntaxError
490 .. attribute:: message
492 The error message as utf-8 bytestring.
494 .. attribute:: lineno
496 The line number where the error occurred
500 The load name for the template as unicode string.
502 .. attribute:: filename
504 The filename that loaded the template as bytestring in the encoding
505 of the file system (most likely utf-8 or mbcs on Windows systems).
507 The reason why the filename and error message are bytestrings and not
508 unicode strings is that Python 2.x is not using unicode for exceptions
509 and tracebacks as well as the compiler. This will change with Python 3.
511 .. autoexception:: jinja2.TemplateAssertionError
519 Custom filters are just regular Python functions that take the left side of
520 the filter as first argument and the the arguments passed to the filter as
521 extra arguments or keyword arguments.
523 For example in the filter ``{{ 42|myfilter(23) }}`` the function would be
524 called with ``myfilter(42, 23)``. Here for example a simple filter that can
525 be applied to datetime objects to format them::
527 def datetimeformat(value, format='%H:%M / %d-%m-%Y'):
528 return value.strftime(format)
530 You can register it on the template environment by updating the
531 :attr:`~Environment.filters` dict on the environment::
533 environment.filters['datetimeformat'] = datetimeformat
535 Inside the template it can then be used as follows:
537 .. sourcecode:: jinja
539 written on: {{ article.pub_date|datetimeformat }}
540 publication date: {{ article.pub_date|datetimeformat('%d-%m-%Y') }}
542 Filters can also be passed the current template context or environment. This
543 is useful if a filter wants to return an undefined value or check the current
544 :attr:`~Environment.autoescape` setting. For this purpose two decorators
545 exist: :func:`environmentfilter` and :func:`contextfilter`.
547 Here a small example filter that breaks a text into HTML line breaks and
548 paragraphs and marks the return value as safe HTML string if autoescaping is
552 from jinja2 import environmentfilter, Markup, escape
554 _paragraph_re = re.compile(r'(?:\r\n|\r|\n){2,}')
557 def nl2br(environment, value):
558 result = u'\n\n'.join(u'<p>%s</p>' % p.replace('\n', '<br>\n')
559 for p in _paragraph_re.split(escape(value)))
560 if environment.autoescape:
561 result = Markup(result)
564 Context filters work the same just that the first argument is the current
565 active :class:`Context` rather then the environment.
573 Tests work like filters just that there is no way for a test to get access
574 to the environment or context and that they can't be chained. The return
575 value of a test should be `True` or `False`. The purpose of a test is to
576 give the template designers the possibility to perform type and conformability
579 Here a simple test that checks if a variable is a prime number::
586 for i in xrange(2, int(math.ceil(math.sqrt(n))) + 1):
592 You can register it on the template environment by updating the
593 :attr:`~Environment.tests` dict on the environment::
595 environment.tests['prime'] = is_prime
597 A template designer can then use the test like this:
599 .. sourcecode:: jinja
604 42 is not a prime number
608 .. _global-namespace:
613 Variables stored in the :attr:`Environment.globals` dict are special as they
614 are available for imported templates too, even if they are imported without
615 context. This is the place where you can put variables and functions
616 that should be available all the time. Additionally :attr:`Template.globals`
617 exist that are variables available to a specific template that are available
618 to all :meth:`~Template.render` calls.
626 The low level API exposes functionality that can be useful to understand some
627 implementation details, debugging purposes or advanced :ref:`extension
628 <jinja-extensions>` techniques. Unless you know exactly what you are doing we
629 don't recommend using any of those.
631 .. automethod:: Environment.lex
633 .. automethod:: Environment.parse
635 .. automethod:: Environment.preprocess
637 .. automethod:: Template.new_context
639 .. method:: Template.root_render_func(context)
641 This is the low level render function. It's passed a :class:`Context`
642 that has to be created by :meth:`new_context` of the same template or
643 a compatible template. This render function is generated by the
644 compiler from the template code and returns a generator that yields
647 If an exception in the template code happens the template engine will
648 not rewrite the exception but pass through the original one. As a
649 matter of fact this function should only be called from within a
650 :meth:`render` / :meth:`generate` / :meth:`stream` call.
652 .. attribute:: Template.blocks
654 A dict of block render functions. Each of these functions works exactly
655 like the :meth:`root_render_func` with the same limitations.
657 .. attribute:: Template.is_up_to_date
659 This attribute is `False` if there is a newer version of the template
660 available, otherwise `True`.
664 The low-level API is fragile. Future Jinja2 versions will try not to
665 change it in a backwards incompatible way but modifications in the Jinja2
666 core may shine through. For example if Jinja2 introduces a new AST node
667 in later versions that may be returned by :meth:`~Environment.parse`.
672 .. versionadded:: 2.2
674 The meta API returns some information about abstract syntax trees that
675 could help applications to implement more advanced template concepts. All
676 the functions of the meta API operate on an abstract syntax tree as
677 returned by the :meth:`Environment.parse` method.
679 .. autofunction:: jinja2.meta.find_undeclared_variables
681 .. autofunction:: jinja2.meta.find_referenced_templates