2009-07-21 09:51:40 +08:00
|
|
|
.. _internals-deprecation:
|
|
|
|
|
|
|
|
|
|
===========================
|
|
|
|
|
Django Deprecation Timeline
|
|
|
|
|
===========================
|
|
|
|
|
|
|
|
|
|
This document outlines when various pieces of Django will be removed, following
|
|
|
|
|
their deprecation, as per the :ref:`Django deprecation policy
|
|
|
|
|
<internal-release-deprecation-policy>`
|
|
|
|
|
|
|
|
|
|
* 1.3
|
|
|
|
|
* ``AdminSite.root()``. This release will remove the old method for
|
|
|
|
|
hooking up admin URLs. This has been deprecated since the 1.1
|
|
|
|
|
release.
|
|
|
|
|
|
2009-12-10 09:05:35 +08:00
|
|
|
* Authentication backends need to define the boolean attribute
|
|
|
|
|
``supports_object_permissions``. The old backend style is deprecated
|
|
|
|
|
since the 1.2 release.
|
|
|
|
|
|
Fixed #9977 - CsrfMiddleware gets template tag added, session dependency removed, and turned on by default.
This is a large change to CSRF protection for Django. It includes:
* removing the dependency on the session framework.
* deprecating CsrfResponseMiddleware, and replacing with a core template tag.
* turning on CSRF protection by default by adding CsrfViewMiddleware to
the default value of MIDDLEWARE_CLASSES.
* protecting all contrib apps (whatever is in settings.py)
using a decorator.
For existing users of the CSRF functionality, it should be a seamless update,
but please note that it includes DEPRECATION of features in Django 1.1,
and there are upgrade steps which are detailed in the docs.
Many thanks to 'Glenn' and 'bthomas', who did a lot of the thinking and work
on the patch, and to lots of other people including Simon Willison and
Russell Keith-Magee who refined the ideas.
Details of the rationale for these changes is found here:
http://code.djangoproject.com/wiki/CsrfProtection
As of this commit, the CSRF code is mainly in 'contrib'. The code will be
moved to core in a separate commit, to make the changeset as readable as
possible.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@11660 bcc190cf-cafb-0310-a4f2-bffc1f526a37
2009-10-27 07:23:07 +08:00
|
|
|
* 1.4
|
|
|
|
|
* ``CsrfResponseMiddleware``. This has been deprecated since the 1.2
|
|
|
|
|
release, in favour of the template tag method for inserting the CSRF
|
|
|
|
|
token. ``CsrfMiddleware``, which combines ``CsrfResponseMiddleware``
|
|
|
|
|
and ``CsrfViewMiddleware``, is also deprecated.
|
|
|
|
|
|
2009-10-27 08:36:34 +08:00
|
|
|
* The old imports for CSRF functionality (``django.contrib.csrf.*``),
|
|
|
|
|
which moved to core in 1.2, will be removed.
|
|
|
|
|
|
2009-11-03 20:53:26 +08:00
|
|
|
* ``SMTPConnection``. The 1.2 release deprecated the ``SMTPConnection``
|
|
|
|
|
class in favor of a generic E-mail backend API.
|
|
|
|
|
|
2009-11-03 22:02:49 +08:00
|
|
|
* The many to many SQL generation functions on the database backends
|
|
|
|
|
will be removed. These have been deprecated since the 1.2 release.
|
|
|
|
|
|
2009-12-10 00:57:23 +08:00
|
|
|
* The ``Message`` model (in ``django.contrib.auth``), its related
|
|
|
|
|
manager in the ``User`` model (``user.message_set``), and the
|
|
|
|
|
associated methods (``user.message_set.create()`` and
|
|
|
|
|
``user.get_and_delete_messages()``), which have
|
|
|
|
|
been deprecated since the 1.2 release, will be removed. The
|
|
|
|
|
:ref:`messages framework <ref-contrib-messages>` should be used
|
|
|
|
|
instead.
|
|
|
|
|
|
2009-12-10 09:05:35 +08:00
|
|
|
* Authentication backends need to support the ``obj`` parameter for
|
|
|
|
|
permission checking. The ``supports_object_permissions`` variable
|
|
|
|
|
is not checked any longer and can be removed.
|
|
|
|
|
|
2009-07-21 09:51:40 +08:00
|
|
|
* 2.0
|
|
|
|
|
* ``django.views.defaults.shortcut()``. This function has been moved
|
|
|
|
|
to ``django.contrib.contenttypes.views.shortcut()`` as part of the
|
|
|
|
|
goal of removing all ``django.contrib`` references from the core
|
|
|
|
|
Django codebase. The old shortcut will be removed in the 2.0
|
|
|
|
|
release.
|
