Removed versionadded/changed annotations dating back to 1.4.

Filters and time zones

~~~~~~~~~~~~~~~~~~~~~~

.. versionadded:: 1.4

If you write a custom filter that operates on :class:`~datetime.datetime`

objects, you'll usually register it with the ``expects_localtime`` flag set to

``True``:

For more information on how the ``takes_context`` option works, see the section

on :ref:`inclusion tags<howto-custom-template-tags-inclusion-tags>`.

.. versionadded:: 1.4

If you need to rename your tag, you can provide a custom name for it:

.. code-block:: python

    def some_function(value):

        return value - 2

.. versionadded:: 1.4

``simple_tag`` functions may accept any number of positional or keyword

arguments. For example:

    # Here, register is a django.template.Library instance, as before

    register.inclusion_tag('results.html')(show_results)

.. versionchanged:: 1.4

Alternatively it is possible to register the inclusion tag using a

:class:`django.template.Template` instance:

``True``, the tag is passed the context object, as in this example. That's the

only difference between this case and the previous ``inclusion_tag`` example.

.. versionadded:: 1.4

``inclusion_tag`` functions may accept any number of positional or keyword

arguments. For example:

Assignment tags

~~~~~~~~~~~~~~~

.. versionadded:: 1.4

To ease the creation of tags setting a variable in the context, Django provides

a helper function, ``assignment_tag``. This function works the same way as

:ref:`simple_tag<howto-custom-template-tags-simple-tags>`, except that it

commonly specified as an object named ``application`` in a Python module

accessible to the server.

.. versionchanged:: 1.4

The :djadmin:`startproject` command creates a :file:`projectname/wsgi.py` that

contains such an application callable.

Filtering error reports

-----------------------

.. versionadded:: 1.4

Filtering sensitive information

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        def my_view(request):

            ...

.. note::

    .. versionchanged:: 1.4

    Since version 1.4, all POST parameters are systematically filtered out of

    error reports for certain :mod:`django.contrib.auth.views` views (

    ``login``, ``password_reset_confirm``, ``password_change``, and

    ``add_view`` and ``user_change_password`` in the ``auth`` admin) to prevent

    the leaking of sensitive information such as user passwords.

    All POST parameters are systematically filtered out of error reports for

    certain :mod:`django.contrib.auth.views` views (``login``,

    ``password_reset_confirm``, ``password_change``, and ``add_view`` and

    ``user_change_password`` in the ``auth`` admin) to prevent the leaking of

    sensitive information such as user passwords.

.. _custom-error-reports:

        Retrieve initial data for the form. By default, returns a copy of

        :attr:`~django.views.generic.edit.FormMixin.initial`.

        .. versionchanged:: 1.4

            In Django 1.3, this method was returning the

            :attr:`~django.views.generic.edit.FormMixin.initial` class variable

            itself.

    .. method:: get_form_class()

        Retrieve the form class to instantiate. By default

    .. attribute:: slug_url_kwarg

        .. versionadded:: 1.4

        The name of the URLConf keyword argument that contains the slug. By

        default, ``slug_url_kwarg`` is ``'slug'``.

    .. attribute:: pk_url_kwarg

        .. versionadded:: 1.4

        The name of the URLConf keyword argument that contains the primary key.

        By default, ``pk_url_kwarg`` is ``'pk'``.