... backend must have supports_priority set 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. Def ... sults ¶ class TaskResultStatus [ソース] ¶ An Enum representing the status of a TaskResult . READY ¶ The Task has just been enqueued, or is ready to be executed again. RUNNING ¶ The Task is currently being executed. FAILED ¶ The Task raised an exception d ... rmation about a specific execution of a Task . Attributes of TaskResult cannot be modified. task ¶ The Task the result was enqueued for. id ¶ A unique identifier for the result, which can be passed to Task.get_result() . The format of the id will depend ... ... backend must have supports_priority set 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. Def ... sults ¶ class TaskResultStatus [ソース] ¶ An Enum representing the status of a TaskResult . READY ¶ The Task has just been enqueued, or is ready to be executed again. RUNNING ¶ The Task is currently being executed. FAILED ¶ The Task raised an exception d ... rmation about a specific execution of a Task . Attributes of TaskResult cannot be modified. task ¶ The Task the result was enqueued for. id ¶ A unique identifier for the result, which can be passed to Task.get_result() . The format of the id will depend ... ... らの接続シグナルを区別するために使用されます。 Tasks signals ¶ New in Django 6.0. Signals sent by the tasks framework. task_enqueued ¶ django.tasks.signals. task_enqueued ¶ Sent once a Task has been enqueued. このシグナルとともに送信される引数は以下の通り ... です: sender The backend class which the Task was enqueued on to. task_result The enqueued TaskResult . task_started ¶ django.tasks.signals. task_started ¶ Sent when a Task has star ... ted executing. このシグナルとともに送信される引数は以下の通りです: sender The backend class which the Task was enqueued on to. task_result The started TaskResult . task_finished ¶ django.tasks.signals. task_finished ¶ Sent once a Task has fin ... ... diate execution ¶ This is the default backend if another is not specified in your settings file. The ImmediateBackend runs enqueued Tasks immediately, rather than in the background. This allows background Task functionality to be slowly added to an appli ... s, to bypass the need to run a real background worker in your tests. ダミーバックエンド ¶ The DummyBackend doesn't execute enqueued Tasks at all, instead storing results for later use. Task results will forever remain in the READY state. This backend is ... ds.dummy.DummyBackend" : TASKS = { "default" : { "BACKEND" : "django.tasks.backends.dummy.DummyBackend" }} The results for enqueued Tasks can be retrieved from the backend's results attribute: >>> from django.tasks import default_task_backend >>> my_task ... ... らの接続シグナルを区別するために使用されます。 Tasks signals ¶ New in Django 6.0. Signals sent by the tasks framework. task_enqueued ¶ django.tasks.signals. task_enqueued ¶ Sent once a Task has been enqueued. このシグナルとともに送信される引数は以下の通り ... です: sender The backend class which the Task was enqueued on to. task_result The enqueued TaskResult . task_started ¶ django.tasks.signals. task_started ¶ Sent when a Task has star ... ted executing. このシグナルとともに送信される引数は以下の通りです: sender The backend class which the Task was enqueued on to. task_result The started TaskResult . task_finished ¶ django.tasks.signals. task_finished ¶ Sent once a Task has fin ... ... diate execution ¶ This is the default backend if another is not specified in your settings file. The ImmediateBackend runs enqueued Tasks immediately, rather than in the background. This allows background Task functionality to be slowly added to an appli ... s, to bypass the need to run a real background worker in your tests. ダミーバックエンド ¶ The DummyBackend doesn't execute enqueued Tasks at all, instead storing results for later use. Task results will forever remain in the READY state. This backend is ... ds.dummy.DummyBackend" : TASKS = { "default" : { "BACKEND" : "django.tasks.backends.dummy.DummyBackend" }} The results for enqueued Tasks can be retrieved from the backend's results attribute: >>> from django.tasks import default_task_backend >>> my_task ... ... il_users ( emails , subject , message ): return send_mail ( subject , message , None , emails ) Once defined, tasks can be enqueued through a configured backend: email_users . enqueue ( emails = [ "user@example.com" ], subject = "You have a message" , me ... ... il_users ( emails , subject , message ): return send_mail ( subject , message , None , emails ) Once defined, tasks can be enqueued through a configured backend: email_users . enqueue ( emails = [ "user@example.com" ], subject = "You have a message" , me ... ... asks.backends.dummy module django.tasks.backends.immediate module django.tasks.exceptions module django.tasks.signals.task_enqueued (組み込み変数) django.tasks.signals.task_finished (組み込み変数) django.tasks.signals.task_started (組み込み変数) django.t ... go.template のクラス) engines (django.template.loader モジュール) enqueue() (BaseTaskBackend のメソッド) (Task のメソッド) enqueued_at (TaskResult の属性) ensure_csrf_cookie() (django.views.decorators.csrf モジュール) Envelope (django.contrib.gis.db.mode ... ... asks.backends.dummy module django.tasks.backends.immediate module django.tasks.exceptions module django.tasks.signals.task_enqueued (組み込み変数) django.tasks.signals.task_finished (組み込み変数) django.tasks.signals.task_started (組み込み変数) django.t ... go.template のクラス) engines (django.template.loader モジュール) enqueue() (BaseTaskBackend のメソッド) (Task のメソッド) enqueued_at (TaskResult の属性) ensure_csrf_cookie() (django.views.decorators.csrf モジュール) Envelope (django.contrib.gis.db.mode ... 2026年10月08日