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.
\nConsultez les notes de publication de Django 2.2 pour plus de détails sur ces changements.
\ndjango.utils.timezone.FixedOffset sera supprimée.
django.core.paginator.QuerySetPaginator sera supprimée.
L’attribut Meta.ordering des modèles n’affectera plus les requêtes GROUP BY.
django.contrib.postgres.fields.FloatRangeField et django.contrib.postgres.forms.FloatRangeField seront supprimés.
Le réglage FILE_CHARSET sera supprimé.
django.contrib.staticfiles.storage.CachedStaticFilesStorage sera supprimée.
RemoteUserBackend.configure_user() exigera request comme premier paramètre positionnel.
La prise en charge de SimpleTestCase.allow_database_queries et de TransactionTestCase.multi_db sera supprimée.
Consultez les notes de publication de Django 2.0 pour plus de détails sur ces changements.
\nLe 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.
\ndjango.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.
La couche de compatibilité pour permettre à InlineModelAdmin.has_add_permission() d’être définie sans paramètre obj sera supprimée.
Consultez les notes de publication de Django 1.11 pour plus de détails sur ces changements.
\ncontrib.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é.
La prise en charge de url() des drapeaux en ligne dans les groupes d’expressions régulières ((?i), (?L), (?m), (?s), and (?u)) sera supprimée.
La prise en charge des méthodes Widget.render() sans le paramètre renderer sera supprimée.
Consultez les notes de publication de Django 1.9 pour plus de détails sur ces changements.
\nLe 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.
La prise en charge des vues d’erreur personnalisées avec un seul paramètre positionnel sera supprimée.
L’attribut mime_type de django.utils.feedgenerator.Atom1Feed et de django.utils.feedgenerator.RssFeed sera supprimé en faveur de content_type.
Le paramètre app_name de django.conf.urls.include() sera supprimé.
Support for passing a 3-tuple as the first argument to include() will\nbe removed.
Support for setting a URL instance namespace without an application\nnamespace will be removed.
Field._get_val_from_obj() will be removed in favor of\nField.value_from_object().
django.template.loaders.eggs.Loader sera supprimée.
Le paramètre current_app de contrib.auth sera supprimé.
The callable_obj keyword argument to\nSimpleTestCase.assertRaisesMessage() will be removed.
Support for the allow_tags attribute on ModelAdmin methods will be\nremoved.
The enclosure keyword argument to SyndicationFeed.add_item() will be\nremoved.
The django.template.loader.LoaderOrigin and\ndjango.template.base.StringOrigin aliases for\ndjango.template.base.Origin will be removed.
Consultez les notes de publication de Django 1.10 pour plus de détails sur ces changements.
\nL’option makemigrations --exit sera supprimée.
Support for direct assignment to a reverse foreign key or many-to-many\nrelation will be removed.
The get_srid() and set_srid() methods of\ndjango.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\nremain 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(),\ncreated_time(), and modified_time() methods will be removed.
Support for query lookups using the model name when\nMeta.default_related_name is set will be removed.
The __search query lookup and the\nDatabaseOperations.fulltext_search_sql() method will be removed.
The shim for supporting custom related manager classes without a\n_apply_rel_filters() method will be removed.
Using User.is_authenticated() and User.is_anonymous() as methods\nwill no longer be supported.
The private attribute virtual_fields of Model._meta will be removed.
The private keyword arguments virtual_only in\nField.contribute_to_class() and virtual in\nModel._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\nparent_link will be removed.
Support for Widget._format_value() will be removed.
FileField methods get_directory_name() and get_filename() will be\nremoved.
The mark_for_escaping() function and the classes it uses: EscapeData,\nEscapeBytes, EscapeText, EscapeString, and EscapeUnicode will\nbe removed.
The escape filter will change to use\ndjango.utils.html.conditional_escape().
Manager.use_for_related_fields sera supprimé.
Model Manager inheritance will follow MRO inheritance rules and the\nMeta.manager_inheritance_from_future to opt-in to this behavior will be\nremoved.
Support for old-style middleware using settings.MIDDLEWARE_CLASSES will\nbe removed.
Consultez les notes de publication de Django 1.8 pour plus de détails sur ces changements.
\nSupport for calling a SQLCompiler directly as an alias for calling its\nquote_name_unless_alias method will be removed.
cycle and firstof template tags will be removed from the future\ntemplate tag library (used during the 1.6/1.7 deprecation period).
django.conf.urls.patterns() sera supprimée.
Support for the prefix argument to\ndjango.conf.urls.i18n.i18n_patterns() will be removed.
SimpleTestCase.urls sera supprimé.
Using an incorrect count of unpacked values in the for template tag\nwill 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\nLOGIN_REDIRECT_URL settings will be removed.
Support for optparse will be dropped for custom management commands\n(replaced by argparse).
The class django.core.management.NoArgsCommand will be removed. Use\nBaseCommand instead, which takes no arguments\nby 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 sera supprimée ; cette fonctionnalité est incluse dans 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 :
\nALLOWED_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()
La vérification des sessions sera active sans tenir compte de la présence de 'django.contrib.auth.middleware.SessionAuthenticationMiddleware' dans 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()\nand Storage.save() to be defined without a max_length argument will\nbe removed.
Support for the legacy %(<foo>)s syntax in ModelFormMixin.success_url\nwill be removed.
Les méthodes d’agrégation GeoQuerySet collect(), extent(), extent3d(), make_line() et unionagg() seront supprimées.
Ability to specify ContentType.name when creating a content type instance\nwill be removed.
Support for the old signature of allow_migrate will be removed. It changed\nfrom allow_migrate(self, db, model) to\nallow_migrate(self, db, app_label, model_name=None, **hints).
Support for the syntax of {% cycle %} that uses comma-separated arguments\nwill be removed.
The warning that Signer issues when given an\ninvalid separator will become an exception.
Consultez les notes de publication de Django 1.7 pour plus de détails sur ces changements.
\ndjango.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\nallow_migrate.
Automatic syncing of apps without migrations will be removed. Migrations will\nbecome compulsory for all apps unless you pass the --run-syncdb option to\nmigrate.
The SQL management commands for apps without migrations, sql, sqlall,\nsqlclear, sqldropindexes, and sqlindexes, will be removed.
Support for automatic loading of initial_data fixtures and initial SQL\ndata will be removed.
All models will need to be defined inside an installed application or\ndeclare an explicit app_label.\nFurthermore, it won’t be possible to import them before their application\nis loaded. In particular, it won’t be possible to import models inside\nthe root package of their application.
The model and form IPAddressField will be removed. A stub field will\nremain for compatibility with historical migrations.
AppCommand.handle_app() will no longer be supported.
RequestSite and get_current_site() will no longer be importable from\ndjango.contrib.sites.models.
FastCGI support via the runfcgi management command will be\nremoved. Please deploy your project using WSGI.
django.utils.datastructures.SortedDict will be removed. Use\ncollections.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\nutils.py in an effort to unify all util and utils references.\nThe 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\nBaseMemcachedCache._get_memcache_timeout() method to\nget_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\nreplaced 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\nto 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\nrequires_system_checks. Admin validators will be replaced by admin\nchecks.
The ModelAdmin.validator_class and default_validator_class attributes\nwill be removed.
ModelAdmin.validate() will be removed.
django.db.backends.DatabaseValidation.validate_field will be removed in\nfavor of the check_field method.
La commande d’administration validate sera supprimée.
django.utils.module_loading.import_by_path sera supprimé en faveur de django.utils.module_loading.import_string.
ssi and url template tags will be removed from the future template\ntag library (used during the 1.3/1.4 deprecation period).
django.utils.text.javascript_quote sera supprimé.
Database test settings as independent entries in the database settings,\nprefixed by TEST_, will no longer be supported.
The cache_choices option to ModelChoiceField and\nModelMultipleChoiceField will be removed.
The default value of the\nRedirectView.permanent\nattribute will change from True to False.
django.contrib.sitemaps.FlatPageSitemap will be removed in favor of\ndjango.contrib.flatpages.sitemaps.FlatPageSitemap.
L’API privée django.test.utils.TestTemplateLoader sera supprimée.
Le module django.contrib.contenttypes.generic sera supprimé.
Les API privées django.db.models.sql.where.WhereNode.make_atom() et django.db.models.sql.where.Constraint seront supprimées.
Consultez les notes de publication de Django 1.6 pour plus de détails sur ces changements.
\ndjango.contrib.comments sera supprimé.
Les API de gestion des transactions suivantes seront supprimées :
\nTransactionMiddleware,
les décorateurs et gestionnaires de contexte autocommit, commit_on_success et commit_manually, définis dans django.db.transaction,
les fonctions commit_unless_managed et rollback_unless_managed, aussi définies dans django.db.transaction,
le réglage TRANSACTIONS_MANAGED.
The cycle and firstof template tags will auto-escape their\narguments. In 1.6 and 1.7, this behavior is provided by the version of these\ntags in the future template tag library.
The SEND_BROKEN_LINK_EMAILS setting will be removed. Add the\ndjango.middleware.common.BrokenLinkEmailsMiddleware middleware to\nyour 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\nand similar queryset methods. This affects the following classes:\nBaseModelAdmin, ChangeList, BaseCommentNode,\nGenericForeignKey, Manager, SingleRelatedObjectDescriptor and\nReverseSingleRelatedObjectDescriptor.
Remove the backward compatible shims introduced to rename the attributes\nChangeList.root_query_set and ChangeList.query_set.
django.views.defaults.shortcut will be removed, as part of the\ngoal of removing all django.contrib references from the core\nDjango codebase. Instead use\ndjango.contrib.contenttypes.views.shortcut. django.conf.urls.shortcut\nwill also be removed.
Le module Python Imaging Library (PIL) ne sera plus pris en charge, car il ne semble plus activement maintenu et qu’il ne fonctionne pas avec Python 3.
Les API privées suivantes seront supprimées :
\ndjango.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 sera supprimé en faveur de django.forms.widgets.RadioChoiceInput.
Le module django.test.simple et la classe django.test.simple.DjangoTestSuiteRunner seront supprimés. Utilisez django.test.runner.DiscoverRunner à la place.
Le module django.test._doctest sera supprimé. Utilisez à la place le module doctest de la bibliothèque Python standard.
Le réglage CACHE_MIDDLEWARE_ANONYMOUS_ONLY sera supprimé.
Usage of the hard-coded Hold down « Control », or « Command » on a Mac, to select\nmore than one. string to override or append to user-provided help_text in\nforms for ManyToMany model fields will not be performed by Django anymore\neither at the model or forms layer.
The Model._meta.get_(add|change|delete)_permission methods will\nbe removed.
The session key django_language will no longer be read for backwards\ncompatibility.
Geographic Sitemaps will be removed\n(django.contrib.gis.sitemaps.views.index and\ndjango.contrib.gis.sitemaps.views.sitemap).
django.utils.html.fix_ampersands, the fix_ampersands template filter and\ndjango.utils.html.clean_html will be removed following an accelerated deprecation.
See the Django 1.5 release notes for more\ndetails on these changes.
\nThe module django.utils.simplejson will be removed. The standard library\nprovides json which should be used instead.
The function django.utils.itercompat.product will be removed. The Python\nbuiltin version should be used instead.
Auto-correction of INSTALLED_APPS and TEMPLATE_DIRS settings when they are\nspecified as a plain string instead of a tuple will be removed and raise an\nexception.
The mimetype argument to the __init__ methods of\nHttpResponse,\nSimpleTemplateResponse, and\nTemplateResponse, will be removed.\ncontent_type should be used instead. This also applies to the\nrender_to_response() shortcut and the sitemap views,\nindex() and\nsitemap().
When HttpResponse is instantiated with an iterator,\nor when content is set to an iterator,\nthat iterator will be immediately consumed.
The AUTH_PROFILE_MODULE setting, and the get_profile() method on\nthe User model, will be removed.
The cleanup management command will be removed. It’s replaced by\nclearsessions.
The daily_cleanup.py script will be removed.
The depth keyword argument will be removed from\nselect_related().
The undocumented get_warnings_state()/restore_warnings_state()\nfunctions from django.test.utils and the save_warnings_state()/\nrestore_warnings_state()\ndjango.test.*TestCase methods are\ndeprecated. Use the warnings.catch_warnings context manager\navailable starting with Python 2.6 instead.
The undocumented check_for_test_cookie method in\nAuthenticationForm will be removed\nfollowing an accelerated deprecation. Users subclassing this form should\nremove calls to this method, and instead ensure that their auth related views\nare CSRF protected, which ensures that cookies are enabled.
The version of django.contrib.auth.views.password_reset_confirm() that\nsupports base36 encoded user IDs\n(django.contrib.auth.views.password_reset_confirm_uidb36) will be\nremoved. If your site has been running Django 1.6 for more than\nPASSWORD_RESET_TIMEOUT_DAYS, this change will have no effect. If\nnot, then any password reset links generated before you upgrade to Django 1.7\nwon’t work after the upgrade.
The django.utils.encoding.StrAndUnicode mix-in will be removed.\nDefine a __str__ method and apply the\npython_2_unicode_compatible() decorator instead.
See the Django 1.4 release notes for more\ndetails on these changes.
\ndjango.contrib.databrowse will be removed.
django.contrib.localflavor will be removed following an accelerated\ndeprecation.
django.contrib.markup will be removed following an accelerated\ndeprecation.
The compatibility modules django.utils.copycompat and\ndjango.utils.hashcompat as well as the functions\ndjango.utils.itercompat.all and django.utils.itercompat.any will\nbe removed. The Python builtin versions should be used instead.
The csrf_response_exempt and csrf_view_exempt decorators will\nbe removed. Since 1.4 csrf_response_exempt has been a no-op (it\nreturns the same function), and csrf_view_exempt has been a\nsynonym for django.views.decorators.csrf.csrf_exempt, which should\nbe used to replace it.
The django.core.cache.backends.memcached.CacheClass backend\nwas split into two in Django 1.3 in order to introduce support for\nPyLibMC. The historical CacheClass will be removed in favor of\ndjango.core.cache.backends.memcached.MemcachedCache.
The UK-prefixed objects of django.contrib.localflavor.uk will only\nbe accessible through their GB-prefixed names (GB is the correct\nISO 3166 code for United Kingdom).
The IGNORABLE_404_STARTS and IGNORABLE_404_ENDS settings have been\nsuperseded by IGNORABLE_404_URLS in the 1.4 release. They will be\nremoved.
The form wizard has been refactored to use class-based views with pluggable\nbackends in 1.4. The previous implementation will be removed.
Legacy ways of calling\ncache_page() will be removed.
The backward-compatibility shim to automatically add a debug-false\nfilter to the 'mail_admins' logging handler will be removed. The\nLOGGING setting should include this filter explicitly if\nit is desired.
The builtin truncation functions django.utils.text.truncate_words()\nand django.utils.text.truncate_html_words() will be removed in\nfavor of the django.utils.text.Truncator class.
The django.contrib.gis.geoip.GeoIP class was moved to\ndjango.contrib.gis.geoip in 1.4 – the shortcut in\ndjango.contrib.gis.utils will be removed.
django.conf.urls.defaults will be removed. The functions\ninclude(), patterns(), and url(), plus\nhandler404 and handler500\nare now available through django.conf.urls.
The functions setup_environ() and execute_manager() will be removed\nfrom django.core.management. This also means that the old (pre-1.4)\nstyle of manage.py file will no longer work.
Setting the is_safe and needs_autoescape flags as attributes of\ntemplate filter functions will no longer be supported.
The attribute HttpRequest.raw_post_data was renamed to HttpRequest.body\nin 1.4. The backward compatibility will be removed –\nHttpRequest.raw_post_data will no longer work.
The value for the post_url_continue parameter in\nModelAdmin.response_add() will have to be either None (to redirect\nto the newly created object’s edit page) or a pre-formatted url. String\nformats, such as the previous default '../%s/', will not be accepted any\nmore.
See the Django 1.3 release notes for more\ndetails on these changes.
\nStarting Django without a SECRET_KEY will result in an exception\nrather than a DeprecationWarning. (This is accelerated from the usual\ndeprecation path; see the Django 1.4 release notes.)
The mod_python request handler will be removed. The mod_wsgi\nhandler should be used instead.
The template attribute on django.test.client.Response\nobjects returned by the test client will be removed.\nThe templates attribute should be\nused instead.
The django.test.simple.DjangoTestRunner will be removed.\nInstead use a unittest-native class. The features of the\ndjango.test.simple.DjangoTestRunner (including fail-fast and\nCtrl-C test termination) can be provided by unittest.TextTestRunner.
The undocumented function\ndjango.contrib.formtools.utils.security_hash will be removed,\ninstead use django.contrib.formtools.utils.form_hmac
The function-based generic view modules will be removed in favor of their\nclass-based equivalents, outlined here.
The django.core.servers.basehttp.AdminMediaHandler will be\nremoved. In its place use\ndjango.contrib.staticfiles.handlers.StaticFilesHandler.
The template tags library adminmedia and the template tag {%\nadmin_media_prefix %} will be removed in favor of the generic static files\nhandling. (This is faster than the usual deprecation path; see the\nDjango 1.4 release notes.)
The url and ssi template tags will be modified so that the first\nargument to each tag is a template variable, not an implied string. In 1.4,\nthis behavior is provided by a version of the tag in the future template\ntag library.
Les commandes d’administration reset et sqlreset seront supprimées.
Authentication backends will need to support an inactive user\nbeing passed to all methods dealing with permissions.\nThe supports_inactive_user attribute will no longer be checked\nand can be removed from custom backends.
transform() will raise\na GEOSException when called\non a geometry with no SRID value.
django.http.CompatCookie will be removed in favor of\ndjango.http.SimpleCookie.
django.core.context_processors.PermWrapper and\ndjango.core.context_processors.PermLookupDict will be removed in\nfavor of the corresponding\ndjango.contrib.auth.context_processors.PermWrapper and\ndjango.contrib.auth.context_processors.PermLookupDict, respectively.
The MEDIA_URL or STATIC_URL settings will be\nrequired to end with a trailing slash to ensure there is a consistent\nway to combine paths in templates.
django.db.models.fields.URLField.verify_exists will be removed. The\nfeature was deprecated in 1.3.1 due to intractable security and\nperformance issues and will follow a slightly accelerated deprecation\ntimeframe.
Translations located under the so-called project path will be ignored during\nthe translation building process performed at runtime. The\nLOCALE_PATHS setting can be used for the same task by including the\nfilesystem path to a locale directory containing non-app-specific\ntranslations in its value.
The Markup contrib app will no longer support versions of Python-Markdown\nlibrary earlier than 2.1. An accelerated timeline was used as this was\na security related deprecation.
The CACHE_BACKEND setting will be removed. The cache backend(s) should be\nspecified in the CACHES setting.
See the Django 1.2 release notes for more\ndetails on these changes.
\nCsrfResponseMiddleware and CsrfMiddleware will be removed. Use\nthe {% csrf_token %} template tag inside forms to enable CSRF\nprotection. CsrfViewMiddleware remains and is enabled by default.
Les anciennes importations de fonctionnalité CSRF (django.contrib.csrf.*), qui sont passées dans le cœur Django dans la version 1.2 seront supprimées.
Le module django.contrib.gis.db.backend sera supprimé en faveur des moteurs spécifiques.
SMTPConnection sera supprimée en faveur d’une API générique de moteur de courriels.
Les fonctions de génération SQL plusieurs-à-plusieurs des moteurs de base de données seront supprimées.
La possibilité d’utiliser la famille de réglages de premier niveau DATABASE_* pour définir les connexions de base de données sera supprimée.
The ability to use shorthand notation to specify a database backend\n(i.e., sqlite3 instead of django.db.backends.sqlite3) will be\nremoved.
The get_db_prep_save, get_db_prep_value and\nget_db_prep_lookup methods will have to support multiple databases.
The Message model (in django.contrib.auth), its related\nmanager in the User model (user.message_set), and the\nassociated methods (user.message_set.create() and\nuser.get_and_delete_messages()), will be removed. The\nmessages framework should be used\ninstead. The related messages variable returned by the\nauth context processor will also be removed. Note that this\nmeans that the admin application will depend on the messages\ncontext processor.
Authentication backends will need to support the obj parameter for\npermission checking. The supports_object_permissions attribute\nwill no longer be checked and can be removed from custom backends.
Authentication backends will need to support the AnonymousUser class\nbeing passed to all methods dealing with permissions. The\nsupports_anonymous_user variable will no longer be checked and can be\nremoved from custom backends.
The ability to specify a callable template loader rather than a\nLoader class will be removed, as will the load_template_source\nfunctions that are included with the built in template loaders for\nbackwards compatibility.
django.utils.translation.get_date_formats() and\ndjango.utils.translation.get_partial_date_formats(). These functions\nwill be removed; use the locale-aware\ndjango.utils.formats.get_format() to get the appropriate formats.
In django.forms.fields, the constants: DEFAULT_DATE_INPUT_FORMATS,\nDEFAULT_TIME_INPUT_FORMATS and\nDEFAULT_DATETIME_INPUT_FORMATS will be removed. Use\ndjango.utils.formats.get_format() to get the appropriate\nformats.
The ability to use a function-based test runner will be removed,\nalong with the django.test.simple.run_tests() test runner.
The views.feed() view and feeds.Feed class in\ndjango.contrib.syndication will be removed. The class-based view\nviews.Feed should be used instead.
django.core.context_processors.auth. This release will\nremove the old method in favor of the new method in\ndjango.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\nsupports_inactive_user until version 1.5 when it will be assumed that\nall backends will handle inactive users.
django.db.models.fields.XMLField will be removed. This was\ndeprecated as part of the 1.3 release. An accelerated deprecation\nschedule has been used because the field hasn’t performed any role\nbeyond that of a simple TextField since the removal of oldforms.\nAll uses of XMLField can be replaced with TextField.
The undocumented mixin parameter to the open() method of\ndjango.core.files.storage.Storage (and subclasses) will be removed.
Consultez les notes de publication de Django 1.1 pour plus de détails sur ces changements.
\nAdminSite.root(). This method of hooking up the admin URLs will be\nremoved in favor of including admin.site.urls.
Les moteurs d’authentification doivent définir les attributs booléens supports_object_permissions et supports_anonymous_user jusqu’à la version 1.4, après quoi Django supposera que tous les moteurs savent gérer ces options.