Calendrier d’obsolescence de Django

Ce document présente les échéances où divers aspects de Django seront supprimés ou modifiés de manière non rétrocompatible, après une période d’obsolescence, en accord avec la politique d’obsolescence. Plus de détails sur ces différents éléments sont souvent disponibles dans les notes de publication les précédant de deux versions.

3.0

Consultez les notes de publication de Django 2.0 pour plus de détails sur ces changements.

• Le module django.db.backends.postgresql_psycopg2 sera supprimé.
• django.shortcuts.render_to_response() sera supprimée.
• Le réglage DEFAULT_CONTENT_TYPE sera supprimé.
• HttpRequest.xreadlines() sera supprimée.
• La prise en charge du paramètre context de Field.from_db_value() et de Expression.convert_value() sera supprimée.
• Le paramètre nommé field_name de QuerySet.earliest() et de latest() sera supprimé.

Consultez les notes de publication de Django 2.1 pour plus de détails sur ces changements.

• django.contrib.gis.db.models.functions.ForceRHR sera supprimée.
• django.utils.http.cookie_date() sera supprimée.
• Les bibliothèques de balises de gabarits staticfiles et admin_static seront supprimées.
• django.contrib.staticfiles.templatetags.static() sera supprimée.
• The shim to allow InlineModelAdmin.has_add_permission() to be defined without an obj argument will be removed.

2.1

Consultez les notes de publication de Django 1.11 pour plus de détails sur ces changements.

• contrib.auth.views.login(), logout(), password_change(), password_change_done(), password_reset(), password_reset_done(), password_reset_confirm() et password_reset_complete() seront supprimées.
• Le paramètre extra_context de contrib.auth.views.logout_then_login() sera supprimé.
• django.test.runner.setup_databases() sera supprimée.
• django.utils.translation.string_concat() sera supprimée.
• django.core.cache.backends.memcached.PyLibMCCache ne prendra plus en charge la transmission des réglages de comportement pylibmc comme attributs de premier niveau des OPTIONS.
• Le paramètre host de django.utils.http.is_safe_url() sera supprimé.
• Le masquage des exceptions produites lors du rendu de la balise de gabarit {% include %} sera supprimé.
• DatabaseIntrospection.get_indexes() sera supprimée.
• La méthode authenticate() des moteurs d’authentification exigera request comme premier paramètre positionnel.
• Le décorateur django.db.models.permalink() sera supprimé.
• Le réglage USE_ETAGS sera supprimé. CommonMiddleware et django.utils.cache.patch_response_headers() ne créeront plus d’ETags.
• L’attribut Model._meta.has_auto_field sera supprimé.
• url()”s support for inline flags in regular expression groups ((?i), (?L), (?m), (?s), and (?u)) will be removed.
• La prise en charge des méthodes Widget.render() sans le paramètre renderer sera supprimée.

2.0

Consultez les notes de publication de Django 1.9 pour plus de détails sur ces changements.

• Le paramètre weak de django.dispatch.signals.Signal.disconnect() sera supprimé.
• django.db.backends.base.BaseDatabaseOperations.check_aggregate_support() sera supprimée.
• Le paquet django.forms.extras sera supprimé.
• L’utilitaire assignment_tag sera supprimé.
• Le paramètre host de assertsRedirects sera supprimé. La couche de compatibilité qui permet de considérer les URL absolues égales aux URL relatives lorsque le chemin est identique sera également supprimée.
• Field.rel sera supprimé.
• L’attribut Field.remote_field.to sera supprimé.
• Le paramètre on_delete de ForeignKey et OneToOneField deviendra obligatoire.
• django.db.models.fields.add_lazy_relation() sera supprimée.
• Lorsque la prise en charge des fuseaux horaires est active, les moteurs de base de données qui ne prennent pas en charge les fuseaux horaires ne vont plus convertir les dates/heures avec fuseau en valeurs UTC naïves lorsque de telles valeurs sont transmises en paramètre à des requêtes SQL exécutées en dehors de l’ORM, par exemple avec cursor.execute().
• Le décorateur django.contrib.auth.tests.utils.skipIfCustomUser() sera supprimé.
• Les classes GeoManager et GeoQuerySet seront supprimées.
• Le module django.contrib.gis.geoip sera supprimé.
• Le contrôle supports_recursion pour les chargeurs de gabarit sera supprimé de :
  • 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()
• Les méthodes de chargeur de gabarit load_template() et load_template_sources() seront supprimées.
• Le paramètre template_dirs des chargeurs de gabarit sera supprimé de :
  • 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()
• La méthode django.template.loaders.base.Loader.__call__() sera supprimée.
• Support for custom error views with a single positional parameter will be dropped.
• The mime_type attribute of django.utils.feedgenerator.Atom1Feed and django.utils.feedgenerator.RssFeed will be removed in favor of content_type.
• The app_name argument to django.conf.urls.include() will be removed.
• Support for passing a 3-tuple as the first argument to include() will be removed.
• Support for setting a URL instance namespace without an application namespace will be removed.
• Field._get_val_from_obj() will be removed in favor of Field.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 to SimpleTestCase.assertRaisesMessage() will be removed.
• Support for the allow_tags attribute on ModelAdmin methods will be removed.
• The enclosure keyword argument to SyndicationFeed.add_item() will be removed.
• The django.template.loader.LoaderOrigin and django.template.base.StringOrigin aliases for django.template.base.Origin will be removed.

Consultez les notes de publication de Django 1.10 pour plus de détails sur ces changements.

• L’option makemigrations --exit sera supprimée.
• Support for direct assignment to a reverse foreign key or many-to-many relation will be removed.
• The get_srid() and set_srid() methods of django.contrib.gis.geos.GEOSGeometry will be removed.
• Les méthodes get_x(), set_x(), get_y(), set_y(), get_z() et set_z() de django.contrib.gis.geos.Point seront supprimées.
• Les méthodes get_coords() et set_coords() de django.contrib.gis.geos.Point seront supprimées.
• La propriété cascaded_union de django.contrib.gis.geos.MultiPolygon sera supprimée.
• django.utils.functional.allow_lazy() sera supprimée.
• L’option shell --plain sera supprimée.
• Le module django.core.urlresolvers sera supprimé.
• The model CommaSeparatedIntegerField will be removed. A stub field will remain 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 when Meta.default_related_name is set will be removed.
• The __search query lookup and the DatabaseOperations.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 methods will no longer be supported.
• The private attribute virtual_fields of Model._meta will be removed.
• The private keyword arguments virtual_only in Field.contribute_to_class() and virtual in Model._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 a parent_link will be removed.
• Support for Widget._format_value() will be removed.
• FileField methods get_directory_name() and get_filename() will be removed.
• The mark_for_escaping() function and the classes it uses: EscapeData, EscapeBytes, EscapeText, EscapeString, and EscapeUnicode will be removed.
• The escape filter will change to use django.utils.html.conditional_escape().
• Manager.use_for_related_fields sera supprimé.
• Model Manager inheritance will follow MRO inheritance rules and the Meta.manager_inheritance_from_future to opt-in to this behavior will be removed.
• Support for old-style middleware using settings.MIDDLEWARE_CLASSES will be removed.

1.10

Consultez les notes de publication de Django 1.8 pour plus de détails sur ces changements.

• Support for calling a SQLCompiler directly as an alias for calling its quote_name_unless_alias method will be removed.
• cycle and firstof template tags will be removed from the future template tag library (used during the 1.6/1.7 deprecation period).
• django.conf.urls.patterns() sera supprimée.
• Support for the prefix argument to django.conf.urls.i18n.i18n_patterns() will be removed.
• SimpleTestCase.urls sera supprimé.
• Using an incorrect count of unpacked values in the for template tag will 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 and LOGIN_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. Use BaseCommand instead, which takes no arguments by default.
• Le module django.core.context_processors sera supprimé.
• Le module djangodb.models.sql.aggregates sera supprimé.
• Le module django.contrib.gis.db.models.sql.aggregates sera supprimé.
• Les méthodes et propriétés suivantes de django.db.sql.query.Query seront supprimées :
  • Propriétés : aggregates et aggregate_select
  • Méthodes : add_aggregate, set_aggregate_mask et append_aggregate_mask.
• django.template.resolve_variable sera supprimée.
• Les API privées suivantes seront supprimées de django.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()
• Le paramètre error_message de django.forms.RegexField sera supprimé.
• Le filtre unordered_list ne prendra plus en charge les listes de l’ancien style.
• La prise en charge des paramètres de view sous forme de texte dans url() sera supprimée.
• La couche de rétrocompatibilité pour renommer django.forms.Form._has_changed() en has_changed() sera supprimée.
• Le filtre de gabarit removetags sera supprimé.
• Les fonctions remove_tags() et strip_entities() de django.utils.html seront supprimées.
• Le paramètre is_admin_site de django.contrib.auth.views.password_reset() sera supprimé.
• django.db.models.field.subclassing.SubfieldBase sera supprimée.
• django.utils.checksums will be removed; its functionality is included in django-localflavor 1.1+.
• L’attribut original_content_type_id de django.contrib.admin.helpers.InlineAdminForm sera supprimé.
• La couche de compatibilité pour permettre à FormMixin.get_form() d’être définie sans valeur par défaut pour son paramètre form_class sera supprimée.
• Les réglages suivants seront supprimés :
  • ALLOWED_INCLUDE_ROOTS
  • TEMPLATE_CONTEXT_PROCESSORS
  • TEMPLATE_DEBUG
  • TEMPLATE_DIRS
  • TEMPLATE_LOADERS
  • TEMPLATE_STRING_IF_INVALID
• L’alias de rétrocompatibilité django.template.loader.BaseLoader sera supprimé.
• Les objets de gabarit Django renvoyés par get_template() et select_template() n’accepteront plus de Context dans leur méthode render().
• Les API de réponse de gabarit forceront l’usage de dict et d’objets de gabarit dépendants du moteur au lieu de respectivement Context et de Template.
• Le paramètre current_app sera supprimé des fonction et classes suivantes :
  • django.shortcuts.render()
  • django.template.Context()
  • django.template.RequestContext()
  • django.template.response.TemplateResponse()
• Les paramètres dictionary et context_instance seront supprimés des fonctions suivantes :
  • django.shortcuts.render()
  • django.shortcuts.render_to_response()
  • django.template.loader.render_to_string()
• Le paramètre dirs sera supprimé des fonctions suivantes :
  • 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 in MIDDLEWARE_CLASSES.
• L’attribut privé django.db.models.Field.related sera supprimé.
• L’option --list de la commande d’administration migrate sera supprimée.
• La balise de gabarit ssi sera supprimée.
• La prise en charge de l’opérateur de comparaison = sera supprimée dans la balise de gabarit if.
• The backwards compatibility shims to allow Storage.get_available_name() and Storage.save() to be defined without a max_length argument will be removed.
• Support for the legacy %(<foo>)s syntax in ModelFormMixin.success_url will 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 instance will be removed.
• Support for the old signature of allow_migrate will be removed. It changed from allow_migrate(self, db, model) to allow_migrate(self, db, app_label, model_name=None, **hints).
• Support for the syntax of {% cycle %} that uses comma-separated arguments will be removed.
• The warning that Signer issues when given an invalid separator will become an exception.

1.9

Consultez les notes de publication de Django 1.7 pour plus de détails sur ces changements.

• django.utils.dictconfig sera supprimé.
• django.utils.importlib sera supprimé.
• django.utils.tzinfo sera supprimé.
• django.utils.unittest sera supprimé.
• La commande syncdb sera supprimée.
• django.db.models.signals.pre_syncdb et django.db.models.signals.post_syncdb seront supprimés.
• allow_syncdb on database routers will no longer automatically become allow_migrate.
• Automatic syncing of apps without migrations will be removed. Migrations will become compulsory for all apps unless you pass the --run-syncdb option to migrate.
• 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 SQL data will be removed.
• All models will need to be defined inside an installed application or declare an explicit app_label. Furthermore, it won’t be possible to import them before their application is loaded. In particular, it won’t be possible to import models inside the root package of their application.
• The model and form IPAddressField will be removed. A stub field will remain for compatibility with historical migrations.
• AppCommand.handle_app() will no longer be supported.
• RequestSite and get_current_site() will no longer be importable from django.contrib.sites.models.
• FastCGI support via the runfcgi management command will be removed. Please deploy your project using WSGI.
• django.utils.datastructures.SortedDict will be removed. Use collections.OrderedDict from the Python standard library instead.
• ModelAdmin.declared_fieldsets will be removed.
• Instances of util.py in the Django codebase have been renamed to utils.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 sera supprimé.
• The backward compatibility shim introduced to rename the BaseMemcachedCache._get_memcache_timeout() method to get_backend_timeout() will be removed.
• Les options --natural et -n de dumpdata seront supprimées.
• Le paramètre use_natural_keys de serializers.serialize() sera supprimé.
• L’API privée django.forms.forms.get_declared_fields() sera supprimée.
• La possibilité d’utiliser un composant SplitDateTimeWidget avec DateTimeField sera supprimée.
• La propriété WSGIRequest.REQUEST sera supprimée.
• La classe django.utils.datastructures.MergeDict sera supprimée.
• The zh-cn and zh-tw language codes will be removed and have been replaced 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 entries to 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 of requires_system_checks. Admin validators will be replaced by admin checks.
• The ModelAdmin.validator_class and default_validator_class attributes will be removed.
• ModelAdmin.validate() will be removed.
• django.db.backends.DatabaseValidation.validate_field will be removed in favor of the check_field method.
• The validate management command will be removed.
• django.utils.module_loading.import_by_path will be removed in favor of django.utils.module_loading.import_string.
• ssi and url template tags will be removed from the future template tag 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 and ModelMultipleChoiceField will be removed.
• The default value of the RedirectView.permanent attribute will change from True to False.
• django.contrib.sitemaps.FlatPageSitemap will be removed in favor of django.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() and django.db.models.sql.where.Constraint will be removed.

1.8

See the Django 1.6 release notes for more details on these changes.

• django.contrib.comments sera supprimé.
• 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 their arguments. In 1.6 and 1.7, this behavior is provided by the version of these tags in the future template tag library.
• The SEND_BROKEN_LINK_EMAILS setting will be removed. Add the django.middleware.common.BrokenLinkEmailsMiddleware middleware to your MIDDLEWARE_CLASSES setting instead.
• django.middleware.doc.XViewMiddleware sera supprimé. Utilisez django.contrib.admindocs.middleware.XViewMiddleware à la place.
• Model._meta.module_name a été renommé en model_name.
• Remove the backward compatible shims introduced to rename get_query_set and similar queryset methods. This affects the following classes: BaseModelAdmin, ChangeList, BaseCommentNode, GenericForeignKey, Manager, SingleRelatedObjectDescriptor and ReverseSingleRelatedObjectDescriptor.
• Remove the backward compatible shims introduced to rename the attributes ChangeList.root_query_set and ChangeList.query_set.
• django.views.defaults.shortcut will be removed, as part of the goal of removing all django.contrib references from the core Django codebase. Instead use django.contrib.contenttypes.views.shortcut. django.conf.urls.shortcut will also be removed.
• Support for the Python Imaging Library (PIL) module will be removed, as it no 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 of django.forms.widgets.RadioChoiceInput.
• The module django.test.simple and the class django.test.simple.DjangoTestSuiteRunner will be removed. Instead use django.test.runner.DiscoverRunner.
• The module django.test._doctest will be removed. Instead use the doctest module 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 select more than one. string to override or append to user-provided help_text in forms for ManyToMany model fields will not be performed by Django anymore either at the model or forms layer.
• The Model._meta.get_(add|change|delete)_permission methods will be removed.
• The session key django_language will no longer be read for backwards compatibility.
• Geographic Sitemaps will be removed (django.contrib.gis.sitemaps.views.index and django.contrib.gis.sitemaps.views.sitemap).
• django.utils.html.fix_ampersands, the fix_ampersands template filter and django.utils.html.clean_html will be removed following an accelerated deprecation.

1.7

See the Django 1.5 release notes for more details on these changes.

• The module django.utils.simplejson will be removed. The standard library provides json which should be used instead.
• The function django.utils.itercompat.product will be removed. The Python builtin version should be used instead.
• Auto-correction of INSTALLED_APPS and TEMPLATE_DIRS settings when they are specified as a plain string instead of a tuple will be removed and raise an exception.
• The mimetype argument to the __init__ methods of HttpResponse, SimpleTemplateResponse, and TemplateResponse, will be removed. content_type should be used instead. This also applies to the render_to_response() shortcut and the sitemap views, index() and sitemap().
• 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 on the User model, will be removed.
• The cleanup management command will be removed. It’s replaced by clearsessions.
• The daily_cleanup.py script will be removed.
• The depth keyword argument will be removed from select_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 are deprecated. Use the warnings.catch_warnings context manager available starting with Python 2.6 instead.
• The undocumented check_for_test_cookie method in AuthenticationForm will be removed following an accelerated deprecation. Users subclassing this form should remove calls to this method, and instead ensure that their auth related views are CSRF protected, which ensures that cookies are enabled.
• The version of django.contrib.auth.views.password_reset_confirm() that supports base36 encoded user IDs (django.contrib.auth.views.password_reset_confirm_uidb36) will be removed. If your site has been running Django 1.6 for more than PASSWORD_RESET_TIMEOUT_DAYS, this change will have no effect. If not, then any password reset links generated before you upgrade to Django 1.7 won’t work after the upgrade.
• The django.utils.encoding.StrAndUnicode mix-in will be removed. Define a __str__ method and apply the python_2_unicode_compatible() decorator instead.

1.6

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.
• The compatibility modules 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.
• The 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.
• The 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.
• The UK-prefixed objects of django.contrib.localflavor.uk will only be accessible through their GB-prefixed names (GB is the correct ISO 3166 code for United Kingdom).
• The IGNORABLE_404_STARTS and IGNORABLE_404_ENDS settings have been superseded by IGNORABLE_404_URLS in the 1.4 release. They will be removed.
• The form wizard has been refactored to use class-based views with pluggable backends in 1.4. The previous implementation will be removed.
• Legacy ways of calling cache_page() will be removed.
• The backward-compatibility shim to automatically add a debug-false filter to the 'mail_admins' logging handler will be removed. The LOGGING setting should include this filter explicitly if it is desired.
• The builtin truncation functions django.utils.text.truncate_words() and django.utils.text.truncate_html_words() will be removed in favor of the django.utils.text.Truncator class.
• The django.contrib.gis.geoip.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 and handler500 are now available through django.conf.urls.
• The functions 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.
• Setting the is_safe and needs_autoescape flags as attributes of template filter functions will no longer be supported.
• The attribute 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.
• The value for the 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.

1.5

See the Django 1.3 release notes for more details on these changes.

• Starting Django without a 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.)
• The mod_python request handler will be removed. The mod_wsgi handler should be used instead.
• The template attribute on django.test.client.Response objects returned by the test client will be removed. The templates attribute should be used instead.
• The 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 be provided by unittest.TextTestRunner.
• The undocumented function django.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 their class-based equivalents, outlined here.
• The django.core.servers.basehttp.AdminMediaHandler will be removed. In its place use django.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 files handling. (This is faster than the usual deprecation path; see the Django 1.4 release notes.)
• The 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.
• Les commandes d’administration reset et sqlreset seront supprimées.
• Authentication backends will need to support an inactive user being passed to all methods dealing with permissions. The 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.
• The 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.
• Translations located under the so-called project path will be ignored during the translation building process performed at runtime. The 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.
• The Markup contrib app will no longer support versions of Python-Markdown library earlier than 2.1. An accelerated timeline was used as this was a security related deprecation.
• The CACHE_BACKEND setting will be removed. The cache backend(s) should be specified in the CACHES setting.

1.4

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.
• 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 favor of 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 backends will be removed.
• The ability to use the DATABASE_* family of top-level settings to define 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 be removed.
• The get_db_prep_save, get_db_prep_value and get_db_prep_lookup methods will have to support multiple databases.
• 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()), 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.
• Authentication backends will need to support the obj parameter for permission checking. The supports_object_permissions attribute will no longer be checked and can be removed from custom backends.
• Authentication backends will need to support the 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.
• The ability to specify a callable template loader rather than a 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.
• In 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.
• 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 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.
• Le moteur de base de données postgresql sera supprimé, utilisez à la place le moteur postgresql_psycopg2.
• Le code de langue no sera supprimé car il a été remplacé par le code de langue nb.
• Authentication backends will need to define the boolean attribute 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.
• The undocumented mixin parameter to the open() method of django.core.files.storage.Storage (and subclasses) will be removed.

1.3

Consultez les notes de publication de Django 1.1 pour plus de détails sur ces changements.

• AdminSite.root(). This method of hooking up the admin URLs will be removed in favor of including admin.site.urls.
• Authentication backends need to define the boolean attributes 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.