  you to host Python code for many template libraries on a single host machine
  without enabling access to all of them for every Django installation.
  
  There's no limit on how many modules you put in the ``templatetags`` package.
  Just keep in mind that a ``{% load %}`` statement will load tags/filters for
  the given Python module name, not the name of the app.
  
  To be a valid tag library, the module must contain a module-level variable
  named ``register`` that is a ``template.Library`` instance, in which all the
  tags and filters are registered. So, near the top of your module, put the
  following::
 
</s> remove order for the ``{% load %}`` tag to work. This is a security feature: It allows
you to host Python code for many template libraries on a single host machine
without enabling access to all of them for every Django installation.
 </s> add order for the :ttag:`{% load %}<load>` tag to work. This is a security feature:
It allows you to host Python code for many template libraries on a single host
machine without enabling access to all of them for every Django installation. </s> remove following::
 </s> add following:

.. code-block:: python </s> remove available to your templates using the ``{% load %}`` tag.
 </s> add available to your templates using the :ttag:`{% load %}<load>` tag. </s> remove information on the node itself. For example, Django provides a builtin ``cycle``
template tag that cycles among a list of given strings each time it's rendered::
 </s> add information on the node itself. For example, Django provides a builtin
``cycle`` template tag that cycles among a list of given strings each time it's
rendered:

.. code-block:: html+django </s> remove       for them using code like::
 </s> add       for them using code like:

      .. code-block:: python
Just keep in mind that a :ttag:`{% load %}<load>` statement will load
tags/filters for the given Python module name, not the name of the app.
  you to host Python code for many template libraries on a single host machine
  without enabling access to all of them for every Django installation.
  
  There's no limit on how many modules you put in the ``templatetags`` package.
Just keep in mind that a :ttag:`{% load %}<load>` statement will load
tags/filters for the given Python module name, not the name of the app.
Just keep in mind that a :ttag:`{% load %}<load>` statement will load
tags/filters for the given Python module name, not the name of the app.
  
  To be a valid tag library, the module must contain a module-level variable
  named ``register`` that is a ``template.Library`` instance, in which all the
  tags and filters are registered. So, near the top of your module, put the
  following::
keep keep keep keep replace replace keep keep keep keep keep
 Brushed up the custom template tag 'howto' guide by moving the assignment_tag doc to a more appropriate place (i.e. under the "Setting a variable in the context" section), adding cross references, fixing a few minor inaccuracies and doing a little PEP8 cleanup.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16909 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/howto/custom-template-tags.txt