Django Deprecation Timeline

This document outlines when various pieces of Django will be removed or alteredin a backward incompatible way, following their deprecation, as per thedeprecation policy. More detailsabout each item can often be found in the release notes of two versions prior.

3.1

See the Django 2.2 release notes for moredetails on these changes.

  • django.utils.timezone.FixedOffset will be removed.
  • django.core.paginator.QuerySetPaginator will be removed.
  • A model's Meta.ordering will no longer affect GROUP BY queries.
  • django.contrib.postgres.fields.FloatRangeField anddjango.contrib.postgres.forms.FloatRangeField will be removed.
  • The FILE_CHARSET setting will be removed.
  • django.contrib.staticfiles.storage.CachedStaticFilesStorage will beremoved.
  • RemoteUserBackend.configure_user() will require request as the firstpositional argument.
  • Support for SimpleTestCase.allow_database_queries andTransactionTestCase.multi_db will be removed.

3.0

See the Django 2.0 release notes for moredetails on these changes.

  • The django.db.backends.postgresql_psycopg2 module will be removed.
  • django.shortcuts.render_to_response() will be removed.
  • The DEFAULT_CONTENT_TYPE setting will be removed.
  • HttpRequest.xreadlines() will be removed.
  • Support for the context argument of Field.from_db_value() andExpression.convert_value() will be removed.

  • The field_name keyword argument of QuerySet.earliest() andlatest() will be removed.
    See the Django 2.1 release notes for moredetails on these changes.

  • django.contrib.gis.db.models.functions.ForceRHR will be removed.

  • django.utils.http.cookie_date() will be removed.
  • The staticfiles and admin_static template tag libraries will beremoved.
  • django.contrib.staticfiles.templatetags.static() will be removed.
  • The shim to allow InlineModelAdmin.has_add_permission() to be definedwithout an obj argument will be removed.

2.1

See the Django 1.11 release notes for moredetails on these changes.

  • contrib.auth.views.login(), logout(), password_change(),password_change_done(), password_reset(), password_reset_done(),password_reset_confirm(), and password_reset_complete() will beremoved.
  • The extra_context parameter of contrib.auth.views.logout_then_login()will be removed.
  • django.test.runner.setup_databases() will be removed.
  • django.utils.translation.string_concat() will be removed.
  • django.core.cache.backends.memcached.PyLibMCCache will no longer supportpassing pylibmc behavior settings as top-level attributes of OPTIONS.
  • The host parameter of django.utils.http.is_safe_url() will beremoved.
  • Silencing of exceptions raised while rendering the {% include %} templatetag will be removed.
  • DatabaseIntrospection.get_indexes() will be removed.
  • The authenticate() method of authentication backends will requirerequest as the first positional argument.
  • The django.db.models.permalink() decorator will be removed.
  • The USE_ETAGS setting will be removed. CommonMiddleware anddjango.utils.cache.patch_response_headers() will no longer set ETags.
  • The Model._meta.has_auto_field attribute will be removed.
  • url()'s support for inline flags in regular expression groups ((?i),(?L), (?m), (?s), and (?u)) will be removed.
  • Support for Widget.render() methods without the renderer argumentwill be removed.

2.0

See the Django 1.9 release notes for moredetails on these changes.

  • The weak argument to django.dispatch.signals.Signal.disconnect() willbe removed.
  • django.db.backends.base.BaseDatabaseOperations.check_aggregate_support()will be removed.
  • The django.forms.extras package will be removed.
  • The assignment_tag helper will be removed.
  • The host argument to assertsRedirects will be removed. Thecompatibility layer which allows absolute URLs to be considered equal torelative ones when the path is identical will also be removed.
  • Field.rel will be removed.
  • Field.remote_field.to attribute will be removed.
  • The on_delete argument for ForeignKey and OneToOneField will berequired.
  • django.db.models.fields.add_lazy_relation() will be removed.
  • When time zone support is enabled, database backends that don't support timezones won't convert aware datetimes to naive values in UTC anymore when suchvalues are passed as parameters to SQL queries executed outside of the ORM,e.g. with cursor.execute().
  • The django.contrib.auth.tests.utils.skipIfCustomUser() decorator will beremoved.
  • The GeoManager and GeoQuerySet classes will be removed.
  • The django.contrib.gis.geoip module will be removed.
  • The supports_recursion check for template loaders will be removed from:
    • django.template.engine.Engine.find_template()
    • django.template.loader_tags.ExtendsNode.find_template()
    • django.template.loaders.base.Loader.supports_recursion()
    • django.template.loaders.cached.Loader.supports_recursion()
  • The load_template() and load_template_sources() template loadermethods will be removed.
  • The template_dirs argument for template loaders will be removed:
    • django.template.loaders.base.Loader.get_template()
    • django.template.loaders.cached.Loader.cache_key()
    • django.template.loaders.cached.Loader.get_template()
    • django.template.loaders.cached.Loader.get_template_sources()
    • django.template.loaders.filesystem.Loader.get_template_sources()
  • The django.template.loaders.base.Loader.call() method will beremoved.
  • Support for custom error views with a single positional parameter will bedropped.
  • The mime_type attribute of django.utils.feedgenerator.Atom1Feed anddjango.utils.feedgenerator.RssFeed will be removed in favor ofcontent_type.
  • The app_name argument to django.conf.urls.include() will beremoved.
  • Support for passing a 3-tuple as the first argument to include() willbe removed.
  • Support for setting a URL instance namespace without an applicationnamespace will be removed.
  • Field._get_val_from_obj() will be removed in favor ofField.value_from_object().
  • django.template.loaders.eggs.Loader will be removed.
  • The current_app parameter to the contrib.auth views will be removed.
  • The callable_obj keyword argument toSimpleTestCase.assertRaisesMessage() will be removed.
  • Support for the allow_tags attribute on ModelAdmin methods will beremoved.
  • The enclosure keyword argument to SyndicationFeed.add_item() will beremoved.

  • The django.template.loader.LoaderOrigin anddjango.template.base.StringOrigin aliases fordjango.template.base.Origin will be removed.
    See the Django 1.10 release notes for moredetails on these changes.

  • The makemigrations —exit option will be removed.

  • Support for direct assignment to a reverse foreign key or many-to-manyrelation will be removed.
  • The get_srid() and set_srid() methods ofdjango.contrib.gis.geos.GEOSGeometry will be removed.
  • The get_x(), set_x(), get_y(), set_y(), get_z(), andset_z() methods of django.contrib.gis.geos.Point will be removed.
  • The get_coords() and set_coords() methods ofdjango.contrib.gis.geos.Point will be removed.
  • The cascaded_union property of django.contrib.gis.geos.MultiPolygonwill be removed.
  • django.utils.functional.allow_lazy() will be removed.
  • The shell —plain option will be removed.
  • The django.core.urlresolvers module will be removed.
  • The model CommaSeparatedIntegerField will be removed. A stub field willremain for compatibility with historical migrations.
  • Support for the template Context.has_key() method will be removed.
  • Support for the django.core.files.storage.Storage.accessed_time(),created_time(), and modified_time() methods will be removed.
  • Support for query lookups using the model name whenMeta.default_related_name is set will be removed.
  • The __search query lookup and theDatabaseOperations.fulltext_search_sql() method will be removed.
  • The shim for supporting custom related manager classes without a_apply_rel_filters() method will be removed.
  • Using User.is_authenticated() and User.is_anonymous() as methodswill no longer be supported.
  • The private attribute virtual_fields of Model._meta will be removed.
  • The private keyword arguments virtual_only inField.contribute_to_class() and virtual inModel._meta.add_field() will be removed.
  • The javascript_catalog() and json_catalog() views will be removed.
  • The django.contrib.gis.utils.precision_wkt() function will be removed.
  • In multi-table inheritance, implicit promotion of a OneToOneField to aparent_link will be removed.
  • Support for Widget._format_value() will be removed.
  • FileField methods get_directory_name() and get_filename() will beremoved.
  • The mark_for_escaping() function and the classes it uses: EscapeData,EscapeBytes, EscapeText, EscapeString, and EscapeUnicode willbe removed.
  • The escape filter will change to usedjango.utils.html.conditional_escape().
  • Manager.use_for_related_fields will be removed.
  • Model Manager inheritance will follow MRO inheritance rules and theMeta.manager_inheritance_from_future to opt-in to this behavior will beremoved.
  • Support for old-style middleware using settings.MIDDLEWARE_CLASSES willbe removed.

1.10

See the Django 1.8 release notes for moredetails on these changes.

  • Support for calling a SQLCompiler directly as an alias for calling itsquote_name_unless_alias method will be removed.
  • cycle and firstof template tags will be removed from the futuretemplate tag library (used during the 1.6/1.7 deprecation period).
  • django.conf.urls.patterns() will be removed.
  • Support for the prefix argument todjango.conf.urls.i18n.i18n_patterns() will be removed.
  • SimpleTestCase.urls will be removed.
  • Using an incorrect count of unpacked values in the for template tagwill raise an exception rather than fail silently.
  • The ability to reverse URLs using a dotted Python path will be removed.
  • The ability to use a dotted Python path for the LOGIN_URL andLOGIN_REDIRECT_URL settings will be removed.
  • Support for optparse will be dropped for custom management commands(replaced by argparse).
  • The class django.core.management.NoArgsCommand will be removed. UseBaseCommand instead, which takes no argumentsby default.
  • django.core.context_processors module will be removed.
  • django.db.models.sql.aggregates module will be removed.
  • django.contrib.gis.db.models.sql.aggregates module will be removed.
  • The following methods and properties of django.db.sql.query.Query willbe removed:
    • Properties: aggregates and aggregate_select
    • Methods: add_aggregate, set_aggregate_mask, andappend_aggregate_mask.
  • django.template.resolve_variable will be removed.
  • The following private APIs will be removed fromdjango.db.models.options.Options (Model._meta):
    • get_field_by_name()
    • get_all_field_names()
    • get_fields_with_model()
    • get_concrete_fields_with_model()
    • get_m2m_with_model()
    • get_all_related_objects()
    • get_all_related_objects_with_model()
    • get_all_related_many_to_many_objects()
    • get_all_related_m2m_objects_with_model()
  • The error_message argument of django.forms.RegexField will be removed.
  • The unordered_list filter will no longer support old style lists.
  • Support for string view arguments to url() will be removed.
  • The backward compatible shim to rename django.forms.Form._has_changed()to has_changed() will be removed.
  • The removetags template filter will be removed.
  • The remove_tags() and strip_entities() functions indjango.utils.html will be removed.
  • The is_admin_site argument todjango.contrib.auth.views.password_reset() will be removed.
  • django.db.models.field.subclassing.SubfieldBase will be removed.
  • django.utils.checksums will be removed; its functionality is includedin django-localflavor 1.1+.
  • The original_content_type_id attribute ondjango.contrib.admin.helpers.InlineAdminForm will be removed.
  • The backwards compatibility shim to allow FormMixin.get_form() to bedefined with no default value for its form_class argument will be removed.
  • The following settings will be removed:
    • ALLOWED_INCLUDE_ROOTS
    • TEMPLATE_CONTEXT_PROCESSORS
    • TEMPLATE_DEBUG
    • TEMPLATE_DIRS
    • TEMPLATE_LOADERS
    • TEMPLATE_STRING_IF_INVALID
  • The backwards compatibility alias django.template.loader.BaseLoader willbe removed.
  • Django template objects returned byget_template() andselect_template() won't accept aContext in theirrender() method anymore.
  • Template response APIs will enforce the useof dict and backend-dependent template objects instead ofContext and Templaterespectively.
  • The current_app parameter for the following function and classes will beremoved:
    • django.shortcuts.render()
    • django.template.Context()
    • django.template.RequestContext()
    • django.template.response.TemplateResponse()
  • The dictionary and context_instance parameters for the followingfunctions will be removed:
    • django.shortcuts.render()
    • django.shortcuts.render_to_response()
    • django.template.loader.render_to_string()
  • The dirs parameter for the following functions will be removed:
    • django.template.loader.get_template()
    • django.template.loader.select_template()
    • django.shortcuts.render()
    • django.shortcuts.render_to_response()
  • Session verification will be enabled regardless of whether or not'django.contrib.auth.middleware.SessionAuthenticationMiddleware' is inMIDDLEWARE_CLASSES.
  • Private attribute django.db.models.Field.related will be removed.
  • The —list option of the migrate management command will be removed.
  • The ssi template tag will be removed.
  • Support for the = comparison operator in the if template tag will beremoved.
  • The backwards compatibility shims to allow Storage.get_available_name()and Storage.save() to be defined without a max_length argument willbe removed.
  • Support for the legacy %(<foo>)s syntax in ModelFormMixin.success_urlwill be removed.
  • GeoQuerySet aggregate methods collect(), extent(), extent3d(),make_line(), and unionagg() will be removed.
  • Ability to specify ContentType.name when creating a content type instancewill be removed.
  • Support for the old signature of allow_migrate will be removed. It changedfrom allow_migrate(self, db, model) toallow_migrate(self, db, app_label, model_name=None, **hints).
  • Support for the syntax of {% cycle %} that uses comma-separated argumentswill be removed.
  • The warning that Signer issues when given aninvalid separator will become an exception.

1.9

See the Django 1.7 release notes for moredetails on these changes.

  • django.utils.dictconfig will be removed.
  • django.utils.importlib will be removed.
  • django.utils.tzinfo will be removed.
  • django.utils.unittest will be removed.
  • The syncdb command will be removed.
  • django.db.models.signals.pre_syncdb anddjango.db.models.signals.post_syncdb will be removed.
  • allow_syncdb on database routers will no longer automatically becomeallow_migrate.
  • Automatic syncing of apps without migrations will be removed. Migrations willbecome compulsory for all apps unless you pass the —run-syncdb option tomigrate.
  • The SQL management commands for apps without migrations, sql, sqlall,sqlclear, sqldropindexes, and sqlindexes, will be removed.
  • Support for automatic loading of initial_data fixtures and initial SQLdata will be removed.
  • All models will need to be defined inside an installed application ordeclare an explicit app_label.Furthermore, it won't be possible to import them before their applicationis loaded. In particular, it won't be possible to import models insidethe root package of their application.
  • The model and form IPAddressField will be removed. A stub field willremain for compatibility with historical migrations.
  • AppCommand.handle_app() will no longer be supported.
  • RequestSite and get_current_site() will no longer be importable fromdjango.contrib.sites.models.
  • FastCGI support via the runfcgi management command will beremoved. Please deploy your project using WSGI.
  • django.utils.datastructures.SortedDict will be removed. Usecollections.OrderedDict from the Python standard library instead.
  • ModelAdmin.declared_fieldsets will be removed.
  • Instances of util.py in the Django codebase have been renamed toutils.py in an effort to unify all util and utils references.The modules that provided backwards compatibility will be removed:
    • django.contrib.admin.util
    • django.contrib.gis.db.backends.util
    • django.db.backends.util
    • django.forms.util
  • ModelAdmin.get_formsets will be removed.
  • The backward compatibility shim introduced to rename theBaseMemcachedCache._get_memcache_timeout() method toget_backend_timeout() will be removed.
  • The —natural and -n options for dumpdata will be removed.
  • The use_natural_keys argument for serializers.serialize() will beremoved.
  • Private API django.forms.forms.get_declared_fields() will be removed.
  • The ability to use a SplitDateTimeWidget with DateTimeField will beremoved.
  • The WSGIRequest.REQUEST property will be removed.
  • The class django.utils.datastructures.MergeDict will be removed.
  • The zh-cn and zh-tw language codes will be removed and have beenreplaced by the zh-hans and zh-hant language code respectively.
  • The internal django.utils.functional.memoize will be removed.
  • django.core.cache.get_cache will be removed. Add suitable entriesto CACHES and use django.core.cache.caches instead.
  • django.db.models.loading will be removed.
  • Passing callable arguments to querysets will no longer be possible.
  • BaseCommand.requires_model_validation will be removed in favor ofrequires_system_checks. Admin validators will be replaced by adminchecks.
  • The ModelAdmin.validator_class and default_validator_class attributeswill be removed.
  • ModelAdmin.validate() will be removed.
  • django.db.backends.DatabaseValidation.validate_field will be removed infavor of the check_field method.
  • The validate management command will be removed.
  • django.utils.module_loading.import_by_path will be removed in favor ofdjango.utils.module_loading.import_string.
  • ssi and url template tags will be removed from the future templatetag library (used during the 1.3/1.4 deprecation period).
  • django.utils.text.javascript_quote will be removed.
  • Database test settings as independent entries in the database settings,prefixed by TEST_, will no longer be supported.
  • The cache_choices option to ModelChoiceField andModelMultipleChoiceField will be removed.
  • The default value of theRedirectView.permanentattribute will change from True to False.
  • django.contrib.sitemaps.FlatPageSitemap will be removed in favor ofdjango.contrib.flatpages.sitemaps.FlatPageSitemap.
  • Private API django.test.utils.TestTemplateLoader will be removed.
  • The django.contrib.contenttypes.generic module will be removed.
  • Private APIs django.db.models.sql.where.WhereNode.make_atom() anddjango.db.models.sql.where.Constraint will be removed.

1.8

See the Django 1.6 release notes for moredetails on these changes.

  • django.contrib.comments will be removed.
  • The following transaction management APIs will be removed:
    • TransactionMiddleware,
    • the decorators and context managers autocommit, commit_on_success,and commit_manually, defined in django.db.transaction,
    • the functions commit_unless_managed and rollback_unless_managed,also defined in django.db.transaction,
    • the TRANSACTIONS_MANAGED setting.
  • The cycle and firstof template tags will auto-escape theirarguments. In 1.6 and 1.7, this behavior is provided by the version of thesetags in the future template tag library.
  • The SEND_BROKEN_LINK_EMAILS setting will be removed. Add thedjango.middleware.common.BrokenLinkEmailsMiddleware middleware toyour MIDDLEWARE_CLASSES setting instead.
  • django.middleware.doc.XViewMiddleware will be removed. Usedjango.contrib.admindocs.middleware.XViewMiddleware instead.
  • Model._meta.module_name was renamed to model_name.
  • Remove the backward compatible shims introduced to rename get_query_setand similar queryset methods. This affects the following classes:BaseModelAdmin, ChangeList, BaseCommentNode,GenericForeignKey, Manager, SingleRelatedObjectDescriptor andReverseSingleRelatedObjectDescriptor.
  • Remove the backward compatible shims introduced to rename the attributesChangeList.root_query_set and ChangeList.query_set.
  • django.views.defaults.shortcut will be removed, as part of thegoal of removing all django.contrib references from the coreDjango codebase. Instead usedjango.contrib.contenttypes.views.shortcut. django.conf.urls.shortcutwill also be removed.
  • Support for the Python Imaging Library (PIL) module will be removed, as itno longer appears to be actively maintained & does not work on Python 3.
  • The following private APIs will be removed:
    • django.db.backend
    • django.db.close_connection()
    • django.db.backends.creation.BaseDatabaseCreation.set_autocommit()
    • django.db.transaction.is_managed()
    • django.db.transaction.managed()
  • django.forms.widgets.RadioInput will be removed in favor ofdjango.forms.widgets.RadioChoiceInput.
  • The module django.test.simple and the classdjango.test.simple.DjangoTestSuiteRunner will be removed. Instead usedjango.test.runner.DiscoverRunner.
  • The module django.test._doctest will be removed. Instead use the doctestmodule from the Python standard library.
  • The CACHE_MIDDLEWARE_ANONYMOUS_ONLY setting will be removed.
  • Usage of the hard-coded Hold down "Control", or "Command" on a Mac, to selectmore than one. string to override or append to user-provided help_text informs for ManyToMany model fields will not be performed by Django anymoreeither at the model or forms layer.
  • The Model.meta.get(add|change|delete)_permission methods willbe removed.
  • The session key django_language will no longer be read for backwardscompatibility.
  • Geographic Sitemaps will be removed(django.contrib.gis.sitemaps.views.index anddjango.contrib.gis.sitemaps.views.sitemap).
  • django.utils.html.fix_ampersands, the fix_ampersands template filter anddjango.utils.html.clean_html will be removed following an accelerated deprecation.

1.7

See the Django 1.5 release notes for moredetails on these changes.

  • The module django.utils.simplejson will be removed. The standard libraryprovides json which should be used instead.
  • The function django.utils.itercompat.product will be removed. The Pythonbuiltin version should be used instead.
  • Auto-correction of INSTALLED_APPS and TEMPLATE_DIRS settings when they arespecified as a plain string instead of a tuple will be removed and raise anexception.
  • The mimetype argument to the init methods ofHttpResponse,SimpleTemplateResponse, andTemplateResponse, will be removed.content_type should be used instead. This also applies to therender_to_response() shortcut and the sitemap views,index() andsitemap().
  • When HttpResponse is instantiated with an iterator,or when content is set to an iterator,that iterator will be immediately consumed.
  • The AUTH_PROFILE_MODULE setting, and the get_profile() method onthe User model, will be removed.
  • The cleanup management command will be removed. It's replaced byclearsessions.
  • The daily_cleanup.py script will be removed.
  • The depth keyword argument will be removed fromselect_related().
  • The undocumented get_warnings_state()/restore_warnings_state()functions from django.test.utils and the save_warnings_state()/restore_warnings_state()django.test.*TestCase methods aredeprecated. Use the warnings.catch_warnings context manageravailable starting with Python 2.6 instead.
  • The undocumented check_for_test_cookie method inAuthenticationForm will be removedfollowing an accelerated deprecation. Users subclassing this form shouldremove calls to this method, and instead ensure that their auth related viewsare CSRF protected, which ensures that cookies are enabled.
  • The version of django.contrib.auth.views.password_reset_confirm() thatsupports base36 encoded user IDs(django.contrib.auth.views.password_reset_confirm_uidb36) will beremoved. If your site has been running Django 1.6 for more thanPASSWORD_RESET_TIMEOUT_DAYS, this change will have no effect. Ifnot, then any password reset links generated before you upgrade to Django 1.7won't work after the upgrade.
  • The django.utils.encoding.StrAndUnicode mix-in will be removed.Define a str method and apply thepython_2_unicode_compatible() decorator instead.

1.6

See the Django 1.4 release notes for moredetails on these changes.

  • django.contrib.databrowse will be removed.
  • django.contrib.localflavor will be removed following an accelerateddeprecation.
  • django.contrib.markup will be removed following an accelerateddeprecation.
  • The compatibility modules django.utils.copycompat anddjango.utils.hashcompat as well as the functionsdjango.utils.itercompat.all and django.utils.itercompat.any willbe removed. The Python builtin versions should be used instead.
  • The csrf_response_exempt and csrf_view_exempt decorators willbe removed. Since 1.4 csrf_response_exempt has been a no-op (itreturns the same function), and csrf_view_exempt has been asynonym for django.views.decorators.csrf.csrf_exempt, which shouldbe used to replace it.
  • The django.core.cache.backends.memcached.CacheClass backendwas split into two in Django 1.3 in order to introduce support forPyLibMC. The historical CacheClass will be removed in favor ofdjango.core.cache.backends.memcached.MemcachedCache.
  • The UK-prefixed objects of django.contrib.localflavor.uk will onlybe accessible through their GB-prefixed names (GB is the correctISO 3166 code for United Kingdom).
  • The IGNORABLE_404_STARTS and IGNORABLE_404_ENDS settings have beensuperseded by IGNORABLE_404_URLS in the 1.4 release. They will beremoved.
  • The form wizard has been refactored to use class-based views with pluggablebackends in 1.4. The previous implementation will be removed.
  • Legacy ways of callingcache_page() will be removed.
  • The backward-compatibility shim to automatically add a debug-falsefilter to the 'mail_admins' logging handler will be removed. TheLOGGING setting should include this filter explicitly ifit is desired.
  • The builtin truncation functions django.utils.text.truncate_words()and django.utils.text.truncate_html_words() will be removed infavor of the django.utils.text.Truncator class.
  • The django.contrib.gis.geoip.GeoIP class was moved todjango.contrib.gis.geoip in 1.4 — the shortcut indjango.contrib.gis.utils will be removed.
  • django.conf.urls.defaults will be removed. The functionsinclude(), patterns(), and url(), plushandler404 and handler500are now available through django.conf.urls.
  • The functions setup_environ() and execute_manager() will be removedfrom django.core.management. This also means that the old (pre-1.4)style of manage.py file will no longer work.
  • Setting the is_safe and needs_autoescape flags as attributes oftemplate filter functions will no longer be supported.
  • The attribute HttpRequest.raw_post_data was renamed to HttpRequest.bodyin 1.4. The backward compatibility will be removed —HttpRequest.raw_post_data will no longer work.
  • The value for the post_url_continue parameter inModelAdmin.response_add() will have to be either None (to redirectto the newly created object's edit page) or a pre-formatted url. Stringformats, such as the previous default '../%s/', will not be accepted anymore.

1.5

See the Django 1.3 release notes for moredetails on these changes.

  • Starting Django without a SECRET_KEY will result in an exceptionrather than a DeprecationWarning. (This is accelerated from the usualdeprecation path; see the Django 1.4 release notes.)
  • The mod_python request handler will be removed. The mod_wsgihandler should be used instead.
  • The template attribute on django.test.client.Responseobjects returned by the test client will be removed.The templates attribute should beused instead.
  • The django.test.simple.DjangoTestRunner will be removed.Instead use a unittest-native class. The features of thedjango.test.simple.DjangoTestRunner (including fail-fast andCtrl-C test termination) can be provided by unittest.TextTestRunner.
  • The undocumented functiondjango.contrib.formtools.utils.security_hash will be removed,instead use django.contrib.formtools.utils.form_hmac
  • The function-based generic view modules will be removed in favor of theirclass-based equivalents, outlined here.
  • The django.core.servers.basehttp.AdminMediaHandler will beremoved. In its place usedjango.contrib.staticfiles.handlers.StaticFilesHandler.
  • The template tags library adminmedia and the template tag {%
    admin_media_prefix %}     will be removed in favor of the generic static fileshandling. (This is faster than the usual deprecation path; see theDjango 1.4 release notes.)
  • The url and ssi template tags will be modified so that the firstargument 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 templatetag library.
  • The reset and sqlreset management commands will be removed.
  • Authentication backends will need to support an inactive userbeing passed to all methods dealing with permissions.The supports_inactive_user attribute will no longer be checkedand can be removed from custom backends.
  • transform() will raisea GEOSException when calledon a geometry with no SRID value.
  • django.http.CompatCookie will be removed in favor ofdjango.http.SimpleCookie.
  • django.core.context_processors.PermWrapper anddjango.core.context_processors.PermLookupDict will be removed infavor of the correspondingdjango.contrib.auth.context_processors.PermWrapper anddjango.contrib.auth.context_processors.PermLookupDict, respectively.
  • The MEDIA_URL or STATIC_URL settings will berequired to end with a trailing slash to ensure there is a consistentway to combine paths in templates.
  • django.db.models.fields.URLField.verify_exists will be removed. Thefeature was deprecated in 1.3.1 due to intractable security andperformance issues and will follow a slightly accelerated deprecationtimeframe.
  • Translations located under the so-called project path will be ignored duringthe translation building process performed at runtime. TheLOCALE_PATHS setting can be used for the same task by including thefilesystem path to a locale directory containing non-app-specifictranslations in its value.
  • The Markup contrib app will no longer support versions of Python-Markdownlibrary earlier than 2.1. An accelerated timeline was used as this wasa security related deprecation.
  • The CACHE_BACKEND setting will be removed. The cache backend(s) should bespecified in the CACHES setting.

1.4

See the Django 1.2 release notes for moredetails on these changes.

  • CsrfResponseMiddleware and CsrfMiddleware will be removed. Usethe {% csrf_token %} template tag inside forms to enable CSRFprotection. CsrfViewMiddleware remains and is enabled by default.
  • The old imports for CSRF functionality (django.contrib.csrf.*),which moved to core in 1.2, will be removed.
  • The django.contrib.gis.db.backend module will be removed in favorof the specific backends.
  • SMTPConnection will be removed in favor of a generic Email backend API.
  • The many to many SQL generation functions on the database backendswill be removed.
  • The ability to use the DATABASE_* family of top-level settings todefine database connections will be removed.
  • The ability to use shorthand notation to specify a database backend(i.e., sqlite3 instead of django.db.backends.sqlite3) will beremoved.
  • The get_db_prep_save, get_db_prep_value andget_db_prep_lookup methods will have to support multiple databases.
  • The Message model (in django.contrib.auth), its relatedmanager in the User model (user.message_set), and theassociated methods (user.message_set.create() anduser.get_and_delete_messages()), will be removed. Themessages framework should be usedinstead. The related messages variable returned by theauth context processor will also be removed. Note that thismeans that the admin application will depend on the messagescontext processor.
  • Authentication backends will need to support the obj parameter forpermission checking. The supports_object_permissions attributewill no longer be checked and can be removed from custom backends.
  • Authentication backends will need to support the AnonymousUser classbeing passed to all methods dealing with permissions. Thesupports_anonymous_user variable will no longer be checked and can beremoved from custom backends.
  • The ability to specify a callable template loader rather than aLoader class will be removed, as will the load_template_sourcefunctions that are included with the built in template loaders forbackwards compatibility.
  • django.utils.translation.get_date_formats() anddjango.utils.translation.get_partial_date_formats(). These functionswill be removed; use the locale-awaredjango.utils.formats.get_format() to get the appropriate formats.
  • In django.forms.fields, the constants: DEFAULT_DATE_INPUT_FORMATS,DEFAULT_TIME_INPUT_FORMATS andDEFAULT_DATETIME_INPUT_FORMATS will be removed. Usedjango.utils.formats.get_format() to get the appropriateformats.
  • The ability to use a function-based test runner will be removed,along with the django.test.simple.run_tests() test runner.
  • The views.feed() view and feeds.Feed class indjango.contrib.syndication will be removed. The class-based viewviews.Feed should be used instead.
  • django.core.context_processors.auth. This release willremove the old method in favor of the new method indjango.contrib.auth.context_processors.auth.
  • The postgresql database backend will be removed, use thepostgresql_psycopg2 backend instead.
  • The no language code will be removed and has been replaced by thenb language code.
  • Authentication backends will need to define the boolean attributesupports_inactive_user until version 1.5 when it will be assumed thatall backends will handle inactive users.
  • django.db.models.fields.XMLField will be removed. This wasdeprecated as part of the 1.3 release. An accelerated deprecationschedule has been used because the field hasn't performed any rolebeyond that of a simple TextField since the removal of oldforms.All uses of XMLField can be replaced with TextField.
  • The undocumented mixin parameter to the open() method ofdjango.core.files.storage.Storage (and subclasses) will be removed.

1.3

See the Django 1.1 release notes for moredetails on these changes.

  • AdminSite.root(). This method of hooking up the admin URLs will beremoved in favor of including admin.site.urls.
  • Authentication backends need to define the boolean attributessupports_object_permissions and supports_anonymous_user untilversion 1.4, at which point it will be assumed that all backends willsupport these options.