Removed versionadded/changed annotations for 1.8.

    class NotEqualLookup(Lookup):

        # ...

.. versionchanged:: 1.8

    The ability to use the decorator pattern was added.

We can now use ``foo__ne`` for any field ``foo``. You will need to ensure that

this registration happens before you try to create any querysets using it. You

could place the implementation in a ``models.py`` file, or register the lookup

user-facing content rendering and database population) that require a

project-neutral string language.

.. versionchanged:: 1.8

    In previous versions, Django forced the "en-us" locale instead of

    deactivating translations.

If, for some reason, your custom management command needs to use a fixed locale,

you should manually activate and deactivate it in your

:meth:`~BaseCommand.handle` method using the functions provided by the I18N

.. attribute:: BaseCommand.missing_args_message

    .. versionadded:: 1.8

    If your command defines mandatory positional arguments, you can customize

    the message error returned in the case of missing arguments. The default is

    output by :py:mod:`argparse` ("too few arguments").

.. method:: BaseCommand.add_arguments(parser)

    .. versionadded:: 1.8

    Entry point to add parser arguments to handle command line arguments passed

    to the command. Custom commands should override this method to add both

    positional and optional arguments accepted by the command. Calling

.. warning:: Avoiding XSS vulnerabilities when reusing built-in filters

    .. versionchanged:: 1.8

    Django's built-in filters have ``autoescape=True`` by default in order to

    get the proper autoescaping behavior and avoid a cross-site script

    vulnerability.

        t = context.template.engine.get_template('small_fragment.html')

        return t.render(Context({'var': obj}, autoescape=context.autoescape))

.. versionchanged:: 1.8

    The ``template`` attribute of ``Context`` objects was added in Django 1.8.

    :meth:`context.template.engine.get_template

    <django.template.Engine.get_template>` must be used instead of

    :func:`django.template.loader.get_template` because the latter now returns

    a wrapper whose ``render`` method doesn't accept a

    :class:`~django.template.Context`.

If we had neglected to pass in the current ``context.autoescape`` value to our

new ``Context`` in this example, the results would have *always* been

automatically escaped, which may not be the desired behavior if the template

            migrations.RunPython(forwards),

        ]

.. versionadded:: 1.8

You can also provide hints that will be passed to the :meth:`allow_migrate()`

method of database routers as ``**hints``:

    class MyDeprecatedTests(unittest.TestCase):

        ...

.. versionchanged:: 1.8

    Previous versions of Django had some ``Ignore*DeprecationWarningsMixin``

    classes to prevent warnings from appearing. These have been replaced by the

    ``ignore_warnings`` decorator.

You can also add a test for the deprecation warning. You'll have to disable the

"warning as error" behavior in your test by doing::