This document outlines when various pieces of Django will be removed or altered in a backward incompatible way, following their deprecation, as per the deprecation policy. More details about each item can often be found in the release notes of two versions prior.
See the Django 1.4 release notes for more details on these changes.
django.contrib.databrowse
will be removed.django.contrib.localflavor
will be removed following an accelerated
deprecation.django.contrib.markup
will be removed following an accelerated
deprecation.django.utils.copycompat
and
django.utils.hashcompat
as well as the functions
django.utils.itercompat.all
and django.utils.itercompat.any
will
be removed. The Python builtin versions should be used instead.csrf_response_exempt
and csrf_view_exempt
decorators will
be removed. Since 1.4 csrf_response_exempt
has been a no-op (it
returns the same function), and csrf_view_exempt
has been a
synonym for django.views.decorators.csrf.csrf_exempt
, which should
be used to replace it.django.core.cache.backends.memcached.CacheClass
backend
was split into two in Django 1.3 in order to introduce support for
PyLibMC. The historical CacheClass
will be removed in favor of
django.core.cache.backends.memcached.MemcachedCache
.django.contrib.localflavor.uk
will only
be accessible through their GB-prefixed names (GB is the correct
ISO 3166 code for United Kingdom).IGNORABLE_404_STARTS
and IGNORABLE_404_ENDS
settings have been
superseded by IGNORABLE_404_URLS
in the 1.4 release. They will be
removed.cache_page()
will be removed.'mail_admins'
logging handler will be removed. The
LOGGING
setting should include this filter explicitly if
it is desired.django.utils.text.truncate_words()
and django.utils.text.truncate_html_words()
will be removed in
favor of the django.utils.text.Truncator
class.GeoIP
class was moved to
django.contrib.gis.geoip
in 1.4 – the shortcut in
django.contrib.gis.utils
will be removed.django.conf.urls.defaults
will be removed. The functions
include()
, patterns()
and
url()
plus handler404
,
handler500
, are now available through
django.conf.urls
.setup_environ()
and execute_manager()
will be removed
from django.core.management
. This also means that the old (pre-1.4)
style of manage.py
file will no longer work.is_safe
and needs_autoescape
flags as attributes of
template filter functions will no longer be supported.HttpRequest.raw_post_data
was renamed to HttpRequest.body
in 1.4. The backward compatibility will be removed –
HttpRequest.raw_post_data
will no longer work.post_url_continue
parameter in
ModelAdmin.response_add()
will have to be either None
(to redirect
to the newly created object’s edit page) or a pre-formatted url. String
formats, such as the previous default '../%s/'
, will not be accepted any
more.See the Django 1.3 release notes for more details on these changes.
SECRET_KEY
will result in an exception
rather than a DeprecationWarning
. (This is accelerated from the usual
deprecation path; see the Django 1.4 release notes.)mod_python
request handler will be removed. The mod_wsgi
handler should be used instead.template
attribute on django.test.client.Response
objects returned by the test client will be removed.django.test.simple.DjangoTestRunner
will be removed.
Instead use a unittest-native class. The features of the
django.test.simple.DjangoTestRunner
(including fail-fast and
Ctrl-C test termination) can currently be provided by the unittest-native
TextTestRunner
.django.contrib.formtools.utils.security_hash
will be removed,
instead use django.contrib.formtools.utils.form_hmac
django.core.servers.basehttp.AdminMediaHandler
will be
removed. In its place use
django.contrib.staticfiles.handlers.StaticFilesHandler
.adminmedia
and the template tag {%
admin_media_prefix %}
will be removed in favor of the generic static files
handling. (This is faster than the usual deprecation path; see the
Django 1.4 release notes.)url
and ssi
template tags will be
modified so that the first argument to each tag is a template variable, not
an implied string. In 1.4, this behavior is provided by a version of the tag
in the future
template tag library.reset
and sqlreset
management commands will be removed.supports_inactive_user
attribute will no longer be checked
and can be removed from custom backends.transform()
will raise
a GEOSException
when called
on a geometry with no SRID value.django.http.CompatCookie
will be removed in favor of
django.http.SimpleCookie
.django.core.context_processors.PermWrapper
and
django.core.context_processors.PermLookupDict
will be removed in
favor of the corresponding
django.contrib.auth.context_processors.PermWrapper
and
django.contrib.auth.context_processors.PermLookupDict
, respectively.MEDIA_URL
or STATIC_URL
settings will be
required to end with a trailing slash to ensure there is a consistent
way to combine paths in templates.django.db.models.fields.URLField.verify_exists
will be removed. The
feature was deprecated in 1.3.1 due to intractable security and
performance issues and will follow a slightly accelerated deprecation
timeframe.LOCALE_PATHS
setting can be used for the same task by including the
filesystem path to a locale
directory containing non-app-specific
translations in its value.CACHE_BACKEND
setting will be removed. The cache backend(s) should be
specified in the CACHES
setting.See the Django 1.2 release notes for more details on these changes.
CsrfResponseMiddleware
and CsrfMiddleware
will be removed. Use
the {% csrf_token %}
template tag inside forms to enable CSRF
protection. CsrfViewMiddleware
remains and is enabled by default.django.contrib.csrf.*
),
which moved to core in 1.2, will be removed.django.contrib.gis.db.backend
module will be removed in favor
of the specific backends.SMTPConnection
will be removed in favor of a generic Email backend API.DATABASE_*
family of top-level settings to
define database connections will be removed.sqlite3
instead of django.db.backends.sqlite3
) will be
removed.get_db_prep_save
, get_db_prep_value
and
get_db_prep_lookup
methods will have to support multiple databases.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()
), will be removed. The
messages framework should be used
instead. The related messages
variable returned by the
auth context processor will also be removed. Note that this
means that the admin application will depend on the messages
context processor.obj
parameter for
permission checking. The supports_object_permissions
attribute
will no longer be checked and can be removed from custom backends.AnonymousUser
class
being passed to all methods dealing with permissions. The
supports_anonymous_user
variable will no longer be checked and can be
removed from custom backends.Loader
class will be removed, as will the load_template_source
functions that are included with the built in template loaders for
backwards compatibility.django.utils.translation.get_date_formats()
and
django.utils.translation.get_partial_date_formats()
. These functions
will be removed; use the locale-aware
django.utils.formats.get_format()
to get the appropriate formats.django.forms.fields
, the constants: DEFAULT_DATE_INPUT_FORMATS
,
DEFAULT_TIME_INPUT_FORMATS
and
DEFAULT_DATETIME_INPUT_FORMATS
will be removed. Use
django.utils.formats.get_format()
to get the appropriate
formats.django.test.simple.run_tests()
test runner.views.feed()
view and feeds.Feed
class in
django.contrib.syndication
will be removed. The class-based view
views.Feed
should be used instead.django.core.context_processors.auth
. This release will
remove the old method in favor of the new method in
django.contrib.auth.context_processors.auth
.postgresql
database backend will be removed, use the
postgresql_psycopg2
backend instead.no
language code will be removed and has been replaced by the
nb
language code.supports_inactive_user
until version 1.5 when it will be assumed that
all backends will handle inactive users.django.db.models.fields.XMLField
will be removed. This was
deprecated as part of the 1.3 release. An accelerated deprecation
schedule has been used because the field hasn’t performed any role
beyond that of a simple TextField
since the removal of oldforms
.
All uses of XMLField
can be replaced with TextField
.mixin
parameter to the open()
method of
django.core.files.storage.Storage
(and subclasses) will be removed.See the Django 1.1 release notes for more details on these changes.
AdminSite.root()
. This method of hooking up the admin URLs will be
removed in favor of including admin.site.urls
.supports_object_permissions
and supports_anonymous_user
until
version 1.4, at which point it will be assumed that all backends will
support these options.Oct 03, 2017