... le are supported. Immediate 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 add ... n application, before the required infrastructure is available. To use it, set BACKEND to "django.tasks.backends.immediate.ImmediateBackend" : TASKS = { "default" : { "BACKEND" : "django.tasks.backends.immediate.ImmediateBackend" }} The ImmediateBackend may also ... changing type. For example, consider this Task: @task () def double_dictionary ( key ): return { key : key * 2 } With the ImmediateBackend configured as the default backend: >>> result = double_dictionary . enqueue (( 1 , 2 , 3 )) >>> result . status FAILED >>> ... ... le are supported. Immediate 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 add ... n application, before the required infrastructure is available. To use it, set BACKEND to "django.tasks.backends.immediate.ImmediateBackend" : TASKS = { "default" : { "BACKEND" : "django.tasks.backends.immediate.ImmediateBackend" }} The ImmediateBackend may also ... changing type. For example, consider this Task: @task () def double_dictionary ( key ): return { key : key * 2 } With the ImmediateBackend configured as the default backend: >>> result = double_dictionary . enqueue (( 1 , 2 , 3 )) >>> result . status FAILED >>> ... ... ered by their priority . The below table notes which of the built-in backends support which features: Feature DummyBackend ImmediateBackend supports_defer Yes No supports_async_task Yes Yes supports_get_result No No [ 1 ] supports_priority Yes [ 2 ] Yes [ 3 ] Av ... ackends. These support local execution and inspection, for production ready backends refer to Configuring a Task backend . Immediate backend ¶ class ImmediateBackend [ソース] ¶ The immediate backend executes Tasks immediately, rather than in the background. ダミ ... [ソース] ¶ Raised by get_result() when the provided result_id is for a different Task than the current Task. 脚注 [ 1 ] The ImmediateBackend doesn't officially support get_result() , despite implementing the API, since the result cannot be retrieved from a differ ... ... ered by their priority . The below table notes which of the built-in backends support which features: Feature DummyBackend ImmediateBackend supports_defer Yes No supports_async_task Yes Yes supports_get_result No No [ 1 ] supports_priority Yes [ 2 ] Yes [ 3 ] Av ... ackends. These support local execution and inspection, for production ready backends refer to Configuring a Task backend . Immediate backend ¶ class ImmediateBackend [ソース] ¶ The immediate backend executes Tasks immediately, rather than in the background. ダミ ... [ソース] ¶ Raised by get_result() when the provided result_id is for a different Task than the current Task. 脚注 [ 1 ] The ImmediateBackend doesn't officially support get_result() , despite implementing the API, since the result cannot be retrieved from a differ ... ... とは 結合されません 。 TASKS ¶ New in Django 6.0. デフォルト値: { "default" : { "BACKEND" : "django.tasks.backends.immediate.ImmediateBackend" , } } A dictionary containing the settings for all Task backends to be used with Django. It is a nested dictionary whose ... sks backend to use. The built-in backends are: 'django.tasks.backends.dummy.DummyBackend' 'django.tasks.backends.immediate.ImmediateBackend' You can use a backend that doesn't ship with Django by setting BACKEND to a fully-qualified path of a backend class (i.e. ... ... とは 結合されません 。 TASKS ¶ New in Django 6.0. デフォルト値: { "default" : { "BACKEND" : "django.tasks.backends.immediate.ImmediateBackend" , } } A dictionary containing the settings for all Task backends to be used with Django. It is a nested dictionary whose ... sks backend to use. The built-in backends are: 'django.tasks.backends.dummy.DummyBackend' 'django.tasks.backends.immediate.ImmediateBackend' You can use a backend that doesn't ship with Django by setting BACKEND to a fully-qualified path of a backend class (i.e. ... ... _URLS setting ImageField (django.db.models のクラス) (django.forms のクラス) ImageFile (django.core.files.images のクラス) ImmediateBackend (django.tasks.backends.immediate のクラス) import_epsg() (SpatialReference のメソッド) import_proj() (SpatialReference のメ ... ... _URLS setting ImageField (django.db.models のクラス) (django.forms のクラス) ImageFile (django.core.files.images のクラス) ImmediateBackend (django.tasks.backends.immediate のクラス) import_epsg() (SpatialReference のメソッド) import_proj() (SpatialReference のメ ... 2026年10月08日