Fixed #2744 -- Added 'Writing your own context processors' to docs/templates_python.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@3865 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
2170110df9
commit
5e21888822
|
@ -366,6 +366,18 @@ If ``TEMPLATE_CONTEXT_PROCESSORS`` contains this processor, every
|
||||||
`HttpRequest object`_. Note that this processor is not enabled by default;
|
`HttpRequest object`_. Note that this processor is not enabled by default;
|
||||||
you'll have to activate it.
|
you'll have to activate it.
|
||||||
|
|
||||||
|
Writing your own context processors
|
||||||
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
A context processor has a very simple interface: It's just a Python function
|
||||||
|
that takes one argument, an ``HttpRequest`` object, and returns a dictionary
|
||||||
|
that gets added to the template context. Each context processor *must* return
|
||||||
|
a dictionary.
|
||||||
|
|
||||||
|
Custom context processors can live anywhere in your code base. All Django cares
|
||||||
|
about is that your custom context processors are pointed-to by your
|
||||||
|
``TEMPLATE_CONTEXT_PROCESSORS`` setting.
|
||||||
|
|
||||||
Loading templates
|
Loading templates
|
||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue