Being a web framework, Django needs a convenient way to generate HTML\ndynamically. The most common approach relies on templates. A template contains\nthe static parts of the desired HTML output as well as some special syntax\ndescribing how dynamic content will be inserted. For a hands-on example of\ncreating HTML pages with templates, see Tutorial 3.
\nA Django project can be configured with one or several template engines (or\neven zero if you don’t use templates). Django ships built-in backends for its\nown template system, creatively called the Django template language (DTL), and\nfor the popular alternative Jinja2. Backends for other template languages may\nbe available from third-parties. You can also write your own custom backend,\nsee Custom template backend
\nDjango defines a standard API for loading and rendering templates regardless\nof the backend. Loading consists of finding the template for a given identifier\nand preprocessing it, usually compiling it to an in-memory representation.\nRendering means interpolating the template with context data and returning the\nresulting string.
\nThe Django template language is Django’s own\ntemplate system. Until Django 1.8 it was the only built-in option available.\nIt’s a good template library even though it’s fairly opinionated and sports a\nfew idiosyncrasies. If you don’t have a pressing reason to choose another\nbackend, you should use the DTL, especially if you’re writing a pluggable\napplication and you intend to distribute templates. Django’s contrib apps that\ninclude templates, like django.contrib.admin,\nuse the DTL.
\nFor historical reasons, both the generic support for template engines and the\nimplementation of the Django template language live in the django.template\nnamespace.
A Django template is a text document or a Python string marked-up using the\nDjango template language. Some constructs are recognized and interpreted by the\ntemplate engine. The main ones are variables and tags.
\nA template is rendered with a context. Rendering replaces variables with their\nvalues, which are looked up in the context, and executes tags. Everything else\nis output as is.
\nThe syntax of the Django template language involves four constructs.
\nA variable outputs a value from the context, which is a dict-like object\nmapping keys to values.
\nVariables are surrounded by {{ and }} like this:
My first name is {{ first_name }}. My last name is {{ last_name }}.\nWith a context of {'first_name': 'John', 'last_name': 'Doe'}, this template\nrenders to:
My first name is John. My last name is Doe.\nDictionary lookup, attribute lookup and list-index lookups are implemented with\na dot notation:
\n{{ my_dict.key }}\n{{ my_object.attribute }}\n{{ my_list.0 }}\nIf a variable resolves to a callable, the template system will call it with no\narguments and use its result instead of the callable.
\nFilters transform the values of variables and tag arguments.
\nThey look like this:
\n{{ django|title }}\nWith a context of {'django': 'the web framework for perfectionists with\ndeadlines'}, this template renders to:
The Web Framework For Perfectionists With Deadlines\nSome filters take an argument:
\n{{ my_date|date:"Y-m-d" }}\nA reference of built-in filters is\navailable as well as instructions for writing custom filters.
\nComments look like this:
\n{# this won't be rendered #}\nA {% comment %} tag provides multi-line comments.
django.template.Engine encapsulates an instance of the Django\ntemplate system. The main reason for instantiating an\nEngine directly is to use the Django template\nlanguage outside of a Django project.
django.template.backends.django.DjangoTemplates is a thin wrapper\nadapting django.template.Engine to Django’s template backend API.
django.template.Template represents a compiled template. Templates are\nobtained with Engine.get_template() or Engine.from_string().
Likewise django.template.backends.django.Template is a thin wrapper\nadapting django.template.Template to the common template API.
django.template.Context holds some metadata in addition to the context\ndata. It is passed to Template.render() for rendering a template.
django.template.RequestContext is a subclass of\nContext that stores the current\nHttpRequest and runs template context processors.
The common API doesn’t have an equivalent concept. Context data is passed in a\nplain dict and the current HttpRequest is passed\nseparately if needed.
Template loaders are responsible for locating templates, loading them, and\nreturning Template objects.
Django provides several built-in template loaders\nand supports custom template loaders.
\nContext processors are functions that receive the current\nHttpRequest as an argument and return a dict of\ndata to be added to the rendering context.
Their main use is to add common data shared by all templates to the context\nwithout repeating code in every view.
\nDjango provides many built-in context processors,\nand you can implement your own additional context processors, too.
\nTemplates engines are configured with the TEMPLATES setting. It’s a\nlist of configurations, one for each engine. The default value is empty. The\nsettings.py generated by the startproject command defines a\nmore useful value:
TEMPLATES = [\n {\n 'BACKEND': 'django.template.backends.django.DjangoTemplates',\n 'DIRS': [],\n 'APP_DIRS': True,\n 'OPTIONS': {\n # ... some options here ...\n },\n },\n]\nBACKEND is a dotted Python path to a template\nengine class implementing Django’s template backend API. The built-in backends\nare django.template.backends.django.DjangoTemplates and\ndjango.template.backends.jinja2.Jinja2.
Since most engines load templates from files, the top-level configuration for\neach engine contains two common settings:
\nDIRS defines a list of directories where the\nengine should look for template source files, in search order.
APP_DIRS tells whether the engine should\nlook for templates inside installed applications. Each backend defines a\nconventional name for the subdirectory inside applications where its\ntemplates should be stored.
While uncommon, it’s possible to configure several instances of the same\nbackend with different options. In that case you should define a unique\nNAME for each engine.
OPTIONS contains backend-specific settings.
The django.template.loader module defines two functions to load templates.
This function loads the template with the given name and returns a\nTemplate object.
The exact type of the return value depends on the backend that loaded the\ntemplate. Each backend has its own Template class.
get_template() tries each template engine in order until one succeeds.\nIf the template cannot be found, it raises\nTemplateDoesNotExist. If the template is found but\ncontains invalid syntax, it raises\nTemplateSyntaxError.
How templates are searched and loaded depends on each engine’s backend and\nconfiguration.
\nIf you want to restrict the search to a particular template engine, pass\nthe engine’s NAME in the using argument.
select_template() is just like get_template(), except it takes a\nlist of template names. It tries each name in order and returns the first\ntemplate that exists.
If loading a template fails, the following two exceptions, defined in\ndjango.template, may be raised:
This exception is raised when a template cannot be found. It accepts the\nfollowing optional arguments for populating the template postmortem on the debug page:
\nbackendThe template backend instance from which the exception originated.
\ntriedA list of sources that were tried when finding the template. This is\nformatted as a list of tuples containing (origin, status), where\norigin is an origin-like object and\nstatus is a string with the reason the template wasn’t found.
chainA list of intermediate TemplateDoesNotExist\nexceptions raised when trying to load a template. This is used by\nfunctions, such as get_template(), that\ntry to load a given template from multiple engines.
This exception is raised when a template was found but contains errors.
\nTemplate objects returned by get_template() and select_template()\nmust provide a render() method with the following signature:
Renders this template with a given context.
\nIf context is provided, it must be a dict. If it isn’t\nprovided, the engine will render the template with an empty context.
If request is provided, it must be an HttpRequest.\nThen the engine must make it, as well as the CSRF token, available in the\ntemplate. How this is achieved is up to each backend.
Here’s an example of the search algorithm. For this example the\nTEMPLATES setting is:
TEMPLATES = [\n {\n 'BACKEND': 'django.template.backends.django.DjangoTemplates',\n 'DIRS': [\n '/home/html/example.com',\n '/home/html/default',\n ],\n },\n {\n 'BACKEND': 'django.template.backends.jinja2.Jinja2',\n 'DIRS': [\n '/home/html/jinja2',\n ],\n },\n]\nIf you call get_template('story_detail.html'), here are the files Django\nwill look for, in order:
/home/html/example.com/story_detail.html ('django' engine)
/home/html/default/story_detail.html ('django' engine)
/home/html/jinja2/story_detail.html ('jinja2' engine)
If you call select_template(['story_253_detail.html', 'story_detail.html']),\nhere’s what Django will look for:
/home/html/example.com/story_253_detail.html ('django' engine)
/home/html/default/story_253_detail.html ('django' engine)
/home/html/jinja2/story_253_detail.html ('jinja2' engine)
/home/html/example.com/story_detail.html ('django' engine)
/home/html/default/story_detail.html ('django' engine)
/home/html/jinja2/story_detail.html ('jinja2' engine)
When Django finds a template that exists, it stops looking.
\n\nIt’s possible – and preferable – to organize templates in subdirectories\ninside each directory containing templates. The convention is to make a\nsubdirectory for each Django app, with subdirectories within those\nsubdirectories as needed.
\nDo this for your own sanity. Storing all templates in the root level of a\nsingle directory gets messy.
\nTo load a template that’s within a subdirectory, use a slash, like so:
\nget_template('news/story_detail.html')\nUsing the same TEMPLATES option as above, this will attempt to load\nthe following templates:
/home/html/example.com/news/story_detail.html ('django' engine)
/home/html/default/news/story_detail.html ('django' engine)
/home/html/jinja2/news/story_detail.html ('jinja2' engine)
In addition, to cut down on the repetitive nature of loading and rendering\ntemplates, Django provides a shortcut function which automates the process.
\nrender_to_string() loads a template like get_template() and\ncalls its render() method immediately. It takes the following\narguments.
template_nameThe name of the template to load and render. If it’s a list of template\nnames, Django uses select_template() instead of\nget_template() to find the template.
contextA dict to be used as the template’s context for rendering.
requestAn optional HttpRequest that will be available\nduring the template’s rendering process.
usingAn optional template engine NAME. The\nsearch for the template will be restricted to that engine.
Usage example:
\nfrom django.template.loader import render_to_string\nrendered = render_to_string('my_template.html', {'foo': 'bar'})\nSee also the render() shortcut which calls\nrender_to_string() and feeds the result into an\nHttpResponse suitable for returning from a view.
Finally, you can use configured engines directly:
\nTemplate engines are available in django.template.engines:
from django.template import engines\n\ndjango_engine = engines['django']\ntemplate = django_engine.from_string("Hello {{ name }}!")\nThe lookup key — 'django' in this example — is the engine’s\nNAME.
Set BACKEND to\n'django.template.backends.django.DjangoTemplates' to configure a Django\ntemplate engine.
When APP_DIRS is True, DjangoTemplates\nengines look for templates in the templates subdirectory of installed\napplications. This generic name was kept for backwards-compatibility.
DjangoTemplates engines accept the following OPTIONS:
'autoescape': a boolean that controls whether HTML autoescaping is\nenabled.
It defaults to True.
'context_processors': a list of dotted Python paths to callables that\nare used to populate the context when a template is rendered with a request.\nThese callables take a request object as their argument and return a\ndict of items to be merged into the context.
It defaults to an empty list.
\nSee RequestContext for more information.
'debug': a boolean that turns on/off template debug mode. If it is\nTrue, the fancy error page will display a detailed report for any\nexception raised during template rendering. This report contains the\nrelevant snippet of the template with the appropriate line highlighted.
It defaults to the value of the DEBUG setting.
'loaders': a list of dotted Python paths to template loader classes.\nEach Loader class knows how to import templates from a particular\nsource. Optionally, a tuple can be used instead of a string. The first item\nin the tuple should be the Loader class name, and subsequent items are\npassed to the Loader during initialization.
The default depends on the values of DIRS and\nAPP_DIRS.
See Loader types for details.
\n'string_if_invalid': the output, as a string, that the template system\nshould use for invalid (e.g. misspelled) variables.
It defaults to an empty string.
\nSee How invalid variables are handled for details.
\n'file_charset': the charset used to read template files on disk.
It defaults to 'utf-8'.
'libraries': A dictionary of labels and dotted Python paths of template\ntag modules to register with the template engine. This can be used to add\nnew libraries or provide alternate labels for existing ones. For example:
OPTIONS={\n 'libraries': {\n 'myapp_tags': 'path.to.myapp.tags',\n 'admin.urls': 'django.contrib.admin.templatetags.admin_urls',\n },\n}\nLibraries can be loaded by passing the corresponding dictionary key to\nthe {% load %} tag.
'builtins': A list of dotted Python paths of template tag modules to\nadd to built-ins. For example:
OPTIONS={\n 'builtins': ['myapp.builtins'],\n}\nTags and filters from built-in libraries can be used without first calling\nthe {% load %} tag.
Requires Jinja2 to be installed:
\nLinux / macOS
$ python -m pip install Jinja2\nWindows
...\\> py -m pip install Jinja2\nSet BACKEND to\n'django.template.backends.jinja2.Jinja2' to configure a Jinja2 engine.
When APP_DIRS is True, Jinja2 engines\nlook for templates in the jinja2 subdirectory of installed applications.
The most important entry in OPTIONS is\n'environment'. It’s a dotted Python path to a callable returning a Jinja2\nenvironment. It defaults to 'jinja2.Environment'. Django invokes that\ncallable and passes other options as keyword arguments. Furthermore, Django\nadds defaults that differ from Jinja2’s for a few options:
'autoescape': True
'auto_reload': settings.DEBUG
'undefined': DebugUndefined if settings.DEBUG else Undefined
Jinja2 engines also accept the following OPTIONS:
'context_processors': a list of dotted Python paths to callables that\nare used to populate the context when a template is rendered with a request.\nThese callables take a request object as their argument and return a\ndict of items to be merged into the context.
It defaults to an empty list.
\n\nThe default configuration is purposefully kept to a minimum. If a template is\nrendered with a request (e.g. when using render()),\nthe Jinja2 backend adds the globals request, csrf_input, and\ncsrf_token to the context. Apart from that, this backend doesn’t create a\nDjango-flavored environment. It doesn’t know about Django filters and tags.\nIn order to use Django-specific APIs, you must configure them into the\nenvironment.
For example, you can create myproject/jinja2.py with this content:
from django.templatetags.static import static\nfrom django.urls import reverse\n\nfrom jinja2 import Environment\n\n\ndef environment(**options):\n env = Environment(**options)\n env.globals.update({\n 'static': static,\n 'url': reverse,\n })\n return env\nand set the 'environment' option to 'myproject.jinja2.environment'.
Then you could use the following constructs in Jinja2 templates:
\n<img src="{{ static('path/to/company-logo.png') }}" alt="Company Logo">\n\n<a href="{{ url('admin:index') }}">Administration</a>\nThe concepts of tags and filters exist both in the Django template language\nand in Jinja2 but they’re used differently. Since Jinja2 supports passing\narguments to callables in templates, many features that require a template tag\nor filter in Django templates can be achieved by calling a function in Jinja2\ntemplates, as shown in the example above. Jinja2’s global namespace removes the\nneed for template context processors. The Django template language doesn’t have\nan equivalent of Jinja2 tests.
\n