summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
authorJake Howard <git@theorangeone.net>2026-02-19 21:48:23 +0000
committernessita <124304+nessita@users.noreply.github.com>2026-03-03 20:00:46 -0300
commita328c355d9625ecdc8f16b249daebba3c0ac2882 (patch)
treef1cc2b6052ef7a249a46391462e95848e5f4815c /docs/topics
parent4b6c998301fedec279ec97b6547e67c3e88b7ff0 (diff)
Refs #35859 -- Mentioned django-tasks and external resources on docs/topics/tasks.txt.
Diffstat (limited to 'docs/topics')
-rw-r--r--docs/topics/tasks.txt11
1 files changed, 9 insertions, 2 deletions
diff --git a/docs/topics/tasks.txt b/docs/topics/tasks.txt
index 06e83af0bc..d3bc54f6b4 100644
--- a/docs/topics/tasks.txt
+++ b/docs/topics/tasks.txt
@@ -4,6 +4,8 @@ Django's Tasks framework
.. versionadded:: 6.0
+ For older Django versions, the :pypi:`django-tasks` backport is available.
+
For a web application, there's often more than just turning HTTP requests into
HTTP responses. For some functionality, it may be beneficial to run code
outside the request-response cycle.
@@ -113,8 +115,13 @@ Third-party backends
As mentioned at the beginning of this section, Django includes backends
suitable for development and testing only. Production systems should rely on
-backends that supply a worker process and durable queue implementation. To use
-an external Task backend with Django, use the Python import path as the
+backends that supply a worker process and a durable queue implementation.
+Available third-party backends are listed on the `Community Ecosystem page
+<https://www.djangoproject.com/community/ecosystem/#tasks>`__ and the `Tasks
+framework grid from Django Packages
+<https://djangopackages.org/grids/g/task-framework/>`__.
+
+To use an external Task backend with Django, use the Python import path as the
:setting:`BACKEND <TASKS-BACKEND>` of the :setting:`TASKS` setting, like so::
TASKS = {