Removed 'Subclassing Context: Custom subclasses' from docs/templates_python.txt because the same thing can be accomplished using DjangoContext processors
git-svn-id: http://code.djangoproject.com/svn/django/trunk@1924 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
b125cafbfc
commit
6a0ba52223
|
@ -329,28 +329,6 @@ See the `internationalization docs`_ for more.
|
|||
.. _LANGUAGE_CODE setting: http://www.djangoproject.com/documentation/settings/#language-code
|
||||
.. _internationalization docs: http://www.djangoproject.com/documentation/i18n/
|
||||
|
||||
Subclassing Context: Custom subclasses
|
||||
--------------------------------------
|
||||
|
||||
Feel free to subclass ``Context`` yourself if you find yourself wanting to give
|
||||
each template something "automatically." For instance, if you want to give
|
||||
every template automatic access to the current time, use something like this::
|
||||
|
||||
from django.core.template import Context
|
||||
import datetime
|
||||
class TimeContext(Context):
|
||||
def __init__(self, *args, **kwargs):
|
||||
Context.__init__(self, *args, **kwargs)
|
||||
self['current_time'] = datetime.datetime.now()
|
||||
|
||||
This technique has two caveats:
|
||||
|
||||
* You'll have to remember to use ``TimeContext`` instead of ``Context`` in
|
||||
your template-loading code.
|
||||
|
||||
* You'll have to be careful not to set the variable ``current_time`` when
|
||||
you populate this context. If you do, you'll override the other one.
|
||||
|
||||
Loading templates
|
||||
-----------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue