... def my_task (): pass Changed in Django 6.1: Support for passing arbitrary **kwargs to the @task decorator is added. If the defined Task is not valid according to the backend, InvalidTask is raised. See defining tasks for usage examples. Task ¶ class Tas ... k [ソース] ¶ Represents a Task to be run in the background. Tasks should be defined using the task() decorator. Attributes of Task cannot be modified. See modifying Tasks for details. priority ¶ The priorit ... to True to use this feature. backend ¶ The alias of the backend the Task should be enqueued to. This must match a backend defined in BACKEND . queue_name ¶ The name of the queue the Task will be enqueued on to. Defaults to "default" . This must match a ... ... those will of course cause deprecation warnings.) There are two deprecated features that are not supported when MAILERS is defined in a project's settings: Trying to access any of the deprecated EMAIL_* settings on django.conf.settings (e.g., checking s ... path. (Other arguments to get_connection() are still supported, and will simply issue deprecation warnings when MAILERS is defined.) If a third-party package does either of those, projects that use it will not be able to change to the MAILERS setting un ... til the package has been updated. Solving "not available when MAILERS is defined" errors ¶ If either of these errors are raised within a third-party package, that indicates it is not compatible with the ... ... those will of course cause deprecation warnings.) There are two deprecated features that are not supported when MAILERS is defined in a project's settings: Trying to access any of the deprecated EMAIL_* settings on django.conf.settings (e.g., checking s ... path. (Other arguments to get_connection() are still supported, and will simply issue deprecation warnings when MAILERS is defined.) If a third-party package does either of those, projects that use it will not be able to change to the MAILERS setting un ... til the package has been updated. Solving "not available when MAILERS is defined" errors ¶ If either of these errors are raised within a third-party package, that indicates it is not compatible with the ... ... def my_task (): pass Changed in Django 6.1: Support for passing arbitrary **kwargs to the @task decorator is added. If the defined Task is not valid according to the backend, InvalidTask is raised. See defining tasks for usage examples. Task ¶ class Tas ... k [ソース] ¶ Represents a Task to be run in the background. Tasks should be defined using the task() decorator. Attributes of Task cannot be modified. See modifying Tasks for details. priority ¶ The priorit ... to True to use this feature. backend ¶ The alias of the backend the Task should be enqueued to. This must match a backend defined in BACKEND . queue_name ¶ The name of the queue the Task will be enqueued on to. Defaults to "default" . This must match a ... ... ent aid (for projects created with startproject ) or results in a MailerDoesNotExist error (when the MAILERS setting isn't defined). Use the MAILERS setting to tell Django how to send email. For example, to send through an SMTP server running on the loc ... w-deprecated EMAIL_BACKEND and related settings. バージョン 6.1 で非推奨: Until Django 2028, if the MAILERS setting is not defined then the earlier behavior still applies: Django will default to using an SMTP server on localhost (but will issue deprecat ... ion warnings). Starting in Django 2028, attempts to send email without MAILERS defined will result in a MailerDoesNotExist error. Existing projects can opt into the new behavior early by adding MAILERS to sett ... ... ent aid (for projects created with startproject ) or results in a MailerDoesNotExist error (when the MAILERS setting isn't defined). Use the MAILERS setting to tell Django how to send email. For example, to send through an SMTP server running on the loc ... w-deprecated EMAIL_BACKEND and related settings. バージョン 6.1 で非推奨: Until Django 2028, if the MAILERS setting is not defined then the earlier behavior still applies: Django will default to using an SMTP server on localhost (but will issue deprecat ... ion warnings). Starting in Django 2028, attempts to send email without MAILERS defined will result in a MailerDoesNotExist error. Existing projects can opt into the new behavior early by adding MAILERS to sett ... ... lse, with the ready() method of their configuration. Application labels are assigned correctly to models even when they're defined outside of models.py . You don't have to set app_label explicitly any more. It is possible to omit models.py entirely if a ... context managers ¶ Prior to Python 2.7, database cursors could be used as a context manager. The specific backend's cursor defined the behavior of the context manager. The behavior of magic method lookups was changed with Python 2.7 and cursors were no ... g passed into Field constructors - things like custom Storage subclasses, for instance - need to have a deconstruct method defined on them as well , though Django provides a handy class decorator that will work for most applications. App-loading changes ... ... lse, with the ready() method of their configuration. Application labels are assigned correctly to models even when they're defined outside of models.py . You don't have to set app_label explicitly any more. It is possible to omit models.py entirely if a ... context managers ¶ Prior to Python 2.7, database cursors could be used as a context manager. The specific backend's cursor defined the behavior of the context manager. The behavior of magic method lookups was changed with Python 2.7 and cursors were no ... g passed into Field constructors - things like custom Storage subclasses, for instance - need to have a deconstruct method defined on them as well , though Django provides a handy class decorator that will work for most applications. App-loading changes ... ... n defines two complementary headers: Content-Security-Policy : Enforces the CSP policy, blocking content that violates the defined directives. Content-Security-Policy-Report-Only : Reports CSP violations without blocking content, allowing for non-intrus ... st implement your own reporting endpoint or integrate with a third-party monitoring service. CSP 定数 ¶ Django provides predefined constants representing common CSP source expression keywords such as 'self' , 'none' , and 'unsafe-inline' . These constan ... ts are intended for use in the directive values defined in the settings. They are available through the CSP enum, and using them is recommended over raw strings. This helps avoid ... ... n defines two complementary headers: Content-Security-Policy : Enforces the CSP policy, blocking content that violates the defined directives. Content-Security-Policy-Report-Only : Reports CSP violations without blocking content, allowing for non-intrus ... st implement your own reporting endpoint or integrate with a third-party monitoring service. CSP 定数 ¶ Django provides predefined constants representing common CSP source expression keywords such as 'self' , 'none' , and 'unsafe-inline' . These constan ... ts are intended for use in the directive values defined in the settings. They are available through the CSP enum, and using them is recommended over raw strings. This helps avoid ... 2026年10月08日