... go 2028; see Migrating email to mailers . To ease the transition, mail.mailers["default"] works with either MAILERS or the deprecated EMAIL_BACKEND setting defined. The deprecated get_connection() function will also return an instance of the default mailer ... se64. However, existing cache entries containing non-standard or corrupted Base64 data may no longer be readable. Features deprecated in 6.1 ¶ E メール ¶ The EMAIL_BACKEND , EMAIL_FILE_PATH , EMAIL_HOST , EMAIL_HOST_PASSWORD , EMAIL_HOST_USER , EMAIL_PORT ... , EMAIL_USE_TLS , EMAIL_USE_SSL , EMAIL_SSL_CERTFILE , EMAIL_SSL_KEYFILE , and EMAIL_TIMEOUT settings are deprecated. Replace them with a MAILERS configuration dictionary as described in Migrating email to mailers . mail.get_connection() i ... ... go 2028; see Migrating email to mailers . To ease the transition, mail.mailers["default"] works with either MAILERS or the deprecated EMAIL_BACKEND setting defined. The deprecated get_connection() function will also return an instance of the default mailer ... se64. However, existing cache entries containing non-standard or corrupted Base64 data may no longer be readable. Features deprecated in 6.1 ¶ E メール ¶ The EMAIL_BACKEND , EMAIL_FILE_PATH , EMAIL_HOST , EMAIL_HOST_PASSWORD , EMAIL_HOST_USER , EMAIL_PORT ... , EMAIL_USE_TLS , EMAIL_USE_SSL , EMAIL_SSL_CERTFILE , EMAIL_SSL_KEYFILE , and EMAIL_TIMEOUT settings are deprecated. Replace them with a MAILERS configuration dictionary as described in Migrating email to mailers . mail.get_connection() i ... ... roduction database. Migrations are covered in their own documentation , but a few of the key features are: syncdb has been deprecated and replaced by migrate . Don't worry - calls to syncdb will still work as before. A new makemigrations command provides a ... odels and make migrations for them. django.db.models.signals.pre_syncdb and django.db.models.signals.post_syncdb have been deprecated, to be replaced by pre_migrate and post_migrate respectively. These new signals have slightly different arguments. Check t ... migrate , but still performs the same function. Routers with allow_syncdb methods will still work, but that method name is deprecated and you should change it as soon as possible (nothing more than renaming is required). initial_data fixtures are no longer ... ... roduction database. Migrations are covered in their own documentation , but a few of the key features are: syncdb has been deprecated and replaced by migrate . Don't worry - calls to syncdb will still work as before. A new makemigrations command provides a ... odels and make migrations for them. django.db.models.signals.pre_syncdb and django.db.models.signals.post_syncdb have been deprecated, to be replaced by pre_migrate and post_migrate respectively. These new signals have slightly different arguments. Check t ... migrate , but still performs the same function. Routers with allow_syncdb methods will still work, but that method name is deprecated and you should change it as soon as possible (nothing more than renaming is required). initial_data fixtures are no longer ... ... d in production to catch those deprecations. Or carefully review your code (including third-party packages) for use of any deprecated email features. Other updates are needed only for projects or reusable Django libraries that use these specific features: ... * settings: MAILERS = { "default" : { "BACKEND" : ... , # value of EMAIL_BACKEND setting "OPTIONS" : { # values from other deprecated EMAIL_* settings ... , }, }, } For example, to update these settings: EMAIL_BACKEND = "django.core.mail.backends.smtp.Emai ... efaults to 587 with use_tls True. "username" : "user@example.net" , "password" : "password" , }, }, } The complete list of deprecated EMAIL_* settings and where they should be moved in a MAILERS configuration is: EMAIL_BACKEND becomes "BACKEND" . If your s ... ... d in production to catch those deprecations. Or carefully review your code (including third-party packages) for use of any deprecated email features. Other updates are needed only for projects or reusable Django libraries that use these specific features: ... * settings: MAILERS = { "default" : { "BACKEND" : ... , # value of EMAIL_BACKEND setting "OPTIONS" : { # values from other deprecated EMAIL_* settings ... , }, }, } For example, to update these settings: EMAIL_BACKEND = "django.core.mail.backends.smtp.Emai ... efaults to 587 with use_tls True. "username" : "user@example.net" , "password" : "password" , }, }, } The complete list of deprecated EMAIL_* settings and where they should be moved in a MAILERS configuration is: EMAIL_BACKEND becomes "BACKEND" . If your s ... ... ate and apply a database migration. For now, the old fields and transforms are left as a reference to the new ones and are deprecated as of this release . DEFAULT_HASHING_ALGORITHM settings ¶ The new DEFAULT_HASHING_ALGORITHM transitional setting allows sp ... Django 3.1.1+. Once the transition to 3.1 is complete you can stop overriding DEFAULT_HASHING_ALGORITHM . This setting is deprecated as of this release, because support for tokens, cookies, sessions, and signatures that use SHA-1 algorithm will be removed ... IMEOUT setting allows defining the number of seconds a password reset link is valid for. This is encouraged instead of the deprecated PASSWORD_RESET_TIMEOUT_DAYS setting, which will be removed in Django 4.0. The password reset mechanism now uses the SHA-25 ... ... ate and apply a database migration. For now, the old fields and transforms are left as a reference to the new ones and are deprecated as of this release . DEFAULT_HASHING_ALGORITHM settings ¶ The new DEFAULT_HASHING_ALGORITHM transitional setting allows sp ... Django 3.1.1+. Once the transition to 3.1 is complete you can stop overriding DEFAULT_HASHING_ALGORITHM . This setting is deprecated as of this release, because support for tokens, cookies, sessions, and signatures that use SHA-1 algorithm will be removed ... IMEOUT setting allows defining the number of seconds a password reset link is valid for. This is encouraged instead of the deprecated PASSWORD_RESET_TIMEOUT_DAYS setting, which will be removed in Django 4.0. The password reset mechanism now uses the SHA-25 ... ... bility with the old API endpoint where possible. However, API endpoints that aren't part of the new official API have been deprecated and will eventually be removed. Multiple template engines ¶ Django 1.8 defines a stable API for integrating template backe ... acle ¶ Earlier versions of Django granted the CONNECT and RESOURCE roles to the test user on Oracle. These roles have been deprecated, so Django 1.8 uses the specific underlying privileges instead. This changes the privileges required of the main user for ... jects (): to_model = getattr ( relation , "related_model" , relation . model ) Also note that get_all_related_objects() is deprecated in 1.8. データベースバックエンド API ¶ The following changes to the database backend API are documented to assist those wr ... ... bility with the old API endpoint where possible. However, API endpoints that aren't part of the new official API have been deprecated and will eventually be removed. Multiple template engines ¶ Django 1.8 defines a stable API for integrating template backe ... acle ¶ Earlier versions of Django granted the CONNECT and RESOURCE roles to the test user on Oracle. These roles have been deprecated, so Django 1.8 uses the specific underlying privileges instead. This changes the privileges required of the main user for ... jects (): to_model = getattr ( relation , "related_model" , relation . model ) Also note that get_all_related_objects() is deprecated in 1.8. データベースバックエンド API ¶ The following changes to the database backend API are documented to assist those wr ... 2026年10月08日