Extensions¶

Jinja supports extensions that can add extra filters, tests, globals or even extend the parser. The main motivation of extensions is to move often used code into a reusable class like adding support for internationalization.

Adding Extensions¶

Extensions are added to the Jinja environment at creation time. Once the environment is created additional extensions cannot be added. To add an extension pass a list of extension classes or import paths to the extensions parameter of the Environment constructor. The following example creates a Jinja environment with the i18n extension loaded:

jinja_env = Environment(extensions=['jinja2.ext.i18n'])

i18n Extension¶

Import name: jinja2.ext.i18n

The i18n extension can be used in combination with gettext or Babel. When it’s enabled, Jinja provides a trans statement that marks a block as translatable and calls gettext.

After enabling, an application has to provide gettext and ngettext functions, either globally or when rendering. A _() function is added as an alias to the gettext function.

Environment Methods¶

After enabling the extension, the environment provides the following additional methods:

jinja2.Environment.install_gettext_translations(translations, newstyle=False)¶: Installs a translation globally for the environment. The translations object must implement gettext and ngettext (or ugettext and ungettext for Python 2). gettext.NullTranslations, gettext.GNUTranslations, and Babels Translations are supported.

Changed in version 2.5: Added new-style gettext support.

jinja2.Environment.install_null_translations(newstyle=False)¶: Install no-op gettext functions. This is useful if you want to prepare the application for internationalization but don’t want to implement the full system yet.

Changed in version 2.5: Added new-style gettext support.

jinja2.Environment.install_gettext_callables(gettext, ngettext, newstyle=False)¶

Install the given gettext and ngettext callables into the environment. They should behave exactly like gettext.gettext() and gettext.ngettext() (or ugettext and ungettext for Python 2).

If newstyle is activated, the callables are wrapped to work like newstyle callables. See New Style Gettext for more information.

New in version 2.5: Added new-style gettext support.

jinja2.Environment.uninstall_gettext_translations()¶: Uninstall the environment’s globally installed translation.

jinja2.Environment.extract_translations(source)¶

Extract localizable strings from the given template node or source.

For every string found this function yields a (lineno, function, message) tuple, where:

lineno is the number of the line on which the string was found.
function is the name of the gettext function used (if the string was extracted from embedded Python code).
message is the string itself (unicode on Python 2), or a tuple of strings for functions with multiple arguments.

If Babel is installed, see Babel Integration to extract the strings.

For a web application that is available in multiple languages but gives all the users the same language (for example, multilingual forum software installed for a French community), the translation may be installed when the environment is created.

translations = get_gettext_translations()
env = Environment(extensions=["jinja2.ext.i18n"])
env.install_gettext_translations(translations)

The get_gettext_translations function would return the translator for the current configuration, for example by using gettext.find.

The usage of the i18n extension for template designers is covered in the template documentation.

Whitespace Trimming¶

New in version 2.10.

Within {% trans %} blocks, it can be useful to trim line breaks and whitespace so that the block of text looks like a simple string with single spaces in the translation file.

Linebreaks and surrounding whitespace can be automatically trimmed by enabling the ext.i18n.trimmed policy.

New Style Gettext¶

New in version 2.5.

New style gettext calls are less to type, less error prone, and support autoescaping better.

You can use “new style” gettext calls by setting env.newstyle_gettext = True or passing newstyle=True to env.install_translations. They are fully supported by the Babel extraction tool, but might not work as expected with other extraction tools.

With standard gettext calls, string formatting is a separate step done with the |format filter. This requires duplicating work for ngettext calls.

{{ gettext("Hello, World!") }}
{{ gettext("Hello, %(name)s!")|format(name=name) }}
{{ ngettext(
       "%(num)d apple", "%(num)d apples", apples|count
   )|format(num=apples|count) }}

New style gettext make formatting part of the call, and behind the scenes enforce more consistency.

{{ gettext("Hello, World!") }}
{{ gettext("Hello, %(name)s!", name=name) }}
{{ ngettext("%(num)d apple", "%(num)d apples", apples|count) }}

The advantages of newstyle gettext are:

There’s no separate formatting step, you don’t have to remember to use the |format filter.
Only named placeholders are allowed. This solves a common problem translators face because positional placeholders can’t switch positions meaningfully. Named placeholders always carry semantic information about what value goes where.
String formatting is used even if no placeholders are used, which makes all strings use a consistent format. Remember to escape any raw percent signs as %%, such as 100%%.
The translated string is marked safe, formatting performs escaping as needed. Mark a parameter as |safe if it has already been escaped.

Expression Statement¶

Import name: jinja2.ext.do

The “do” aka expression-statement extension adds a simple do tag to the template engine that works like a variable expression but ignores the return value.

Loop Controls¶

Import name: jinja2.ext.loopcontrols

This extension adds support for break and continue in loops. After enabling, Jinja provides those two keywords which work exactly like in Python.

With Statement¶

Import name: jinja2.ext.with_

Changed in version 2.9: This extension is now built-in and no longer does anything.

Autoescape Extension¶

Import name: jinja2.ext.autoescape

Changed in version 2.9: This extension was removed and is now built-in. Enabling the extension no longer does anything.

Debug Extension¶

Import name: jinja2.ext.debug

Adds a {% debug %} tag to dump the current context as well as the available filters and tests. This is useful to see what’s available to use in the template without setting up a debugger.

Writing Extensions¶

By writing extensions you can add custom tags to Jinja. This is a non-trivial task and usually not needed as the default tags and expressions cover all common use cases. The i18n extension is a good example of why extensions are useful. Another one would be fragment caching.

When writing extensions you have to keep in mind that you are working with the Jinja template compiler which does not validate the node tree you are passing to it. If the AST is malformed you will get all kinds of compiler or runtime errors that are horrible to debug. Always make sure you are using the nodes you create correctly. The API documentation below shows which nodes exist and how to use them.

Example Extensions¶

Cache¶

The following example implements a cache tag for Jinja by using the cachelib library:

from jinja2 import nodes
from jinja2.ext import Extension


class FragmentCacheExtension(Extension):
    # a set of names that trigger the extension.
    tags = {"cache"}

    def __init__(self, environment):
        super(FragmentCacheExtension, self).__init__(environment)

        # add the defaults to the environment
        environment.extend(fragment_cache_prefix="", fragment_cache=None)

    def parse(self, parser):
        # the first token is the token that started the tag.  In our case
        # we only listen to ``'cache'`` so this will be a name token with
        # `cache` as value.  We get the line number so that we can give
        # that line number to the nodes we create by hand.
        lineno = next(parser.stream).lineno

        # now we parse a single expression that is used as cache key.
        args = [parser.parse_expression()]

        # if there is a comma, the user provided a timeout.  If not use
        # None as second parameter.
        if parser.stream.skip_if("comma"):
            args.append(parser.parse_expression())
        else:
            args.append(nodes.Const(None))

        # now we parse the body of the cache block up to `endcache` and
        # drop the needle (which would always be `endcache` in that case)
        body = parser.parse_statements(["name:endcache"], drop_needle=True)

        # now return a `CallBlock` node that calls our _cache_support
        # helper method on this extension.
        return nodes.CallBlock(
            self.call_method("_cache_support", args), [], [], body
        ).set_lineno(lineno)

    def _cache_support(self, name, timeout, caller):
        """Helper callback."""
        key = self.environment.fragment_cache_prefix + name

        # try to load the block from the cache
        # if there is no fragment in the cache, render it and store
        # it in the cache.
        rv = self.environment.fragment_cache.get(key)
        if rv is not None:
            return rv
        rv = caller()
        self.environment.fragment_cache.add(key, rv, timeout)
        return rv

And here is how you use it in an environment:

from jinja2 import Environment
from cachelib import SimpleCache

env = Environment(extensions=[FragmentCacheExtension])
env.fragment_cache = SimpleCache()

Inside the template it’s then possible to mark blocks as cacheable. The following example caches a sidebar for 300 seconds:

{% cache 'sidebar', 300 %}
<div class="sidebar">
    ...
</div>
{% endcache %}

Inline `gettext`¶

The following example demonstrates using Extension.filter_stream() to parse calls to the _() gettext function inline with static data without needing Jinja blocks.

<h1>_(Welcome)</h1>
<p>_(This is a paragraph)</p>

It requires the i18n extension to be loaded and configured.

# -*- coding: utf-8 -*-
import re

from jinja2.exceptions import TemplateSyntaxError
from jinja2.ext import Extension
from jinja2.lexer import count_newlines
from jinja2.lexer import Token


_outside_re = re.compile(r"\\?(gettext|_)\(")
_inside_re = re.compile(r"\\?[()]")


class InlineGettext(Extension):
    """This extension implements support for inline gettext blocks::

        <h1>_(Welcome)</h1>
        <p>_(This is a paragraph)</p>

    Requires the i18n extension to be loaded and configured.
    """

    def filter_stream(self, stream):
        paren_stack = 0

        for token in stream:
            if token.type != "data":
                yield token
                continue

            pos = 0
            lineno = token.lineno

            while 1:
                if not paren_stack:
                    match = _outside_re.search(token.value, pos)
                else:
                    match = _inside_re.search(token.value, pos)
                if match is None:
                    break
                new_pos = match.start()
                if new_pos > pos:
                    preval = token.value[pos:new_pos]
                    yield Token(lineno, "data", preval)
                    lineno += count_newlines(preval)
                gtok = match.group()
                if gtok[0] == "\\":
                    yield Token(lineno, "data", gtok[1:])
                elif not paren_stack:
                    yield Token(lineno, "block_begin", None)
                    yield Token(lineno, "name", "trans")
                    yield Token(lineno, "block_end", None)
                    paren_stack = 1
                else:
                    if gtok == "(" or paren_stack > 1:
                        yield Token(lineno, "data", gtok)
                    paren_stack += gtok == ")" and -1 or 1
                    if not paren_stack:
                        yield Token(lineno, "block_begin", None)
                        yield Token(lineno, "name", "endtrans")
                        yield Token(lineno, "block_end", None)
                pos = match.end()

            if pos < len(token.value):
                yield Token(lineno, "data", token.value[pos:])

        if paren_stack:
            raise TemplateSyntaxError(
                "unclosed gettext expression",
                token.lineno,
                stream.name,
                stream.filename,
            )

Extension API¶

Extension¶

Extensions always have to extend the jinja2.ext.Extension class:

class jinja2.ext.Extension(environment)¶

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).

identifier¶: The identifier of the extension. This is always the true import name of the extension class and must not be changed.

tags¶: If the extension implements custom tags this is a set of tag names the extension is listening for.

attr(name, lineno=None)¶

Return an attribute node for the current extension. This is useful to pass constants on extensions to generated template code.

self.attr('_my_attribute', lineno=lineno)

call_method(name, args=None, kwargs=None, dyn_args=None, dyn_kwargs=None, lineno=None)¶: Call a method of the extension. This is a shortcut for attr() + jinja2.nodes.Call.

filter_stream(stream)¶: It’s passed a TokenStream that can be used to filter tokens returned. This method has to return an iterable of Tokens, but it doesn’t have to return a TokenStream.

parse(parser)¶: If any of the tags matched this method is called with the parser as first argument. The token the parser stream is pointing at is the name token that matched. This method has to return one or a list of multiple nodes.

preprocess(source, name, filename=None)¶: This method is called before the actual lexing and can be used to preprocess the source. The filename is optional. The return value must be the preprocessed source.

Parser¶

The parser passed to Extension.parse() provides ways to parse expressions of different types. The following methods may be used by extensions:

class jinja2.parser.Parser(environment, source, name=None, filename=None, state=None)¶

This is the central parsing class Jinja uses. It’s passed to extensions and can be used to parse expressions or statements.

filename¶: The filename of the template the parser processes. This is not the load name of the template. For the load name see name. For templates that were not loaded form the file system this is None.

name¶: The load name of the template.

stream¶: The current TokenStream

fail(msg, lineno=None, exc=<class 'jinja2.exceptions.TemplateSyntaxError'>)¶: Convenience method that raises exc with the message, passed line number or last line number as well as the current name and filename.

free_identifier(lineno=None)¶: Return a new free identifier as InternalName.

parse_assign_target(with_tuple=True, name_only=False, extra_end_rules=None, with_namespace=False)¶: Parse an assignment target. As Jinja allows assignments to tuples, this function can parse all allowed assignment targets. Per default assignments to tuples are parsed, that can be disable however by setting with_tuple to False. If only assignments to names are wanted name_only can be set to True. The extra_end_rules parameter is forwarded to the tuple parsing function. If with_namespace is enabled, a namespace assignment may be parsed.

parse_expression(with_condexpr=True)¶: Parse an expression. Per default all expressions are parsed, if the optional with_condexpr parameter is set to False conditional expressions are not parsed.

parse_statements(end_tokens, drop_needle=False)¶: Parse multiple statements into a list until one of the end tokens is reached. This is used to parse the body of statements as it also parses template data if appropriate. The parser checks first if the current token is a colon and skips it if there is one. Then it checks for the block end and parses until if one of the end_tokens is reached. Per default the active token in the stream at the end of the call is the matched end token. If this is not wanted drop_needle can be set to True and the end token is removed.

parse_tuple(simplified=False, with_condexpr=True, extra_end_rules=None, explicit_parentheses=False)¶

Works like parse_expression but if multiple expressions are delimited by a comma a Tuple node is created. This method could also return a regular expression instead of a tuple if no commas where found.

The default parsing mode is a full tuple. If simplified is True only names and literals are parsed. The no_condexpr parameter is forwarded to parse_expression().

Because tuples do not require delimiters and may end in a bogus comma an extra hint is needed that marks the end of a tuple. For example for loops support tuples between for and in. In that case the extra_end_rules is set to ['name:in'].

explicit_parentheses is true if the parsing was triggered by an expression in parentheses. This is used to figure out if an empty tuple is a valid expression or not.

class jinja2.lexer.TokenStream(generator, name, filename)¶

A token stream is an iterable that yields Tokens. The parser however does not iterate over it but calls next() to go one token ahead. The current active token is stored as current.

current¶: The current Token.

__next__()¶

Go one token ahead and return the old one.

Use the built-in next() instead of calling this directly.

eos¶: Are we at the end of the stream?

expect(expr)¶: Expect a given token type and return it. This accepts the same argument as jinja2.lexer.Token.test().

look()¶: Look at the next token.

next_if(expr)¶: Perform the token test and return the token if it matched. Otherwise the return value is None.

push(token)¶: Push a token back to the stream.

skip(n=1)¶: Got n tokens ahead.

skip_if(expr)¶: Like next_if() but only returns True or False.

class jinja2.lexer.Token¶

Token class.

lineno¶: The line number of the token

type¶: The type of the token. This string is interned so you may compare it with arbitrary strings using the is operator.

value¶: The value of the token.

test(expr)¶: Test a token against a token expression. This can either be a token type or 'token_type:token_value'. This can only test against string values and types.

test_any(*iterable)¶: Test against multiple token expressions.

There is also a utility function in the lexer module that can count newline characters in strings:

jinja2.lexer.count_newlines(value)¶: Count the number of newline characters in the string. This is useful for extensions that filter a stream.

AST¶

The AST (Abstract Syntax Tree) is used to represent a template after parsing. It’s build of nodes that the compiler then converts into executable Python code objects. Extensions that provide custom statements can return nodes to execute custom Python code.

The list below describes all nodes that are currently available. The AST may change between Jinja versions but will stay backwards compatible.

For more information have a look at the repr of jinja2.Environment.parse().

exception jinja2.nodes.Impossible¶: Raised if the node could not perform a requested action.

Extensions¶

Adding Extensions¶

i18n Extension¶

Environment Methods¶

Whitespace Trimming¶

New Style Gettext¶

Expression Statement¶

Loop Controls¶

With Statement¶

Autoescape Extension¶

Debug Extension¶

Writing Extensions¶

Example Extensions¶

Cache¶

Inline `gettext`¶

Extension API¶

Extension¶

Parser¶

AST¶

Contents

Navigation

Extensions¶

Adding Extensions¶

i18n Extension¶

Environment Methods¶

Whitespace Trimming¶

New Style Gettext¶

Expression Statement¶

Loop Controls¶

With Statement¶

Autoescape Extension¶

Debug Extension¶

Writing Extensions¶

Example Extensions¶

Cache¶

Inline gettext¶

Extension API¶

Extension¶

Parser¶

AST¶

Inline `gettext`¶