test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #25804 -- Documented additions to Jinja2 context.

This commit is contained in:
Moritz Sichert 2016-03-13 13:31:11 +01:00 committed by Tim Graham
parent 5695c142d2
commit 6aef986cdb
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/topics/templates.txt
View File

@ -401,10 +401,13 @@ adds defaults that differ from Jinja2's for a few options:
* ``'auto_reload'``: ``settings.DEBUG`` * ``'auto_reload'``: ``settings.DEBUG``
* ``'undefined'``: ``DebugUndefined if settings.DEBUG else Undefined`` * ``'undefined'``: ``DebugUndefined if settings.DEBUG else Undefined``
The default configuration is purposefully kept to a minimum. The ``Jinja2`` The default configuration is purposefully kept to a minimum. If a template is
backend doesn't create a Django-flavored environment. It doesn't know about rendered with a request (e.g. when using :py:func:`~django.shortcuts.render`),
Django context processors, filters, and tags. In order to use Django-specific the ``Jinja2`` backend adds the globals ``request``, ``csrf_input``, and
APIs, you must configure them into the environment. ``csrf_token`` to the context. Apart from that, this backend doesn't create a
Django-flavored environment. It doesn't know about Django context processors,
filters, and tags. In order to use Django-specific APIs, you must configure
them into the environment.
For example, you can create ``myproject/jinja2.py`` with this content:: For example, you can create ``myproject/jinja2.py`` with this content::