  
      {% load poll_extras %}
  
  The app that contains the custom tags must be in :setting:`INSTALLED_APPS` in
  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.
  
  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.
  
 
</s> remove Just keep in mind that a ``{% load %}`` statement will load tags/filters for
the given Python module name, not the name of the app.
 </s> add 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. </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     Any variable set in the context will only be available in the same ``block``
    of the template in which it was assigned. This behavior is intentional;
    it provides a scope for variables so that they don't conflict with
    context in other blocks.
 </s> add     Any variable set in the context will only be available in the same
    ``block`` of the template in which it was assigned. This behavior is
    intentional; it provides a scope for variables so that they don't conflict
    with context in other blocks. </s> remove       for them using code like::
 </s> add       for them using code like:

      .. code-block:: python
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.
  
      {% load poll_extras %}
  
  The app that contains the custom tags must be in :setting:`INSTALLED_APPS` in
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.
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.
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.
  
  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.
  
keep keep keep keep replace 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