summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Smith <39445562+smithdc1@users.noreply.github.com>2020-06-02 13:37:16 +0100
committerCarlton Gibson <carlton.gibson@noumenal.es>2020-06-02 14:38:06 +0200
commit8734a02f5d70d3d324edc96aaa763a6e8b4eb371 (patch)
treeaa0372ee48bac904914dbe6f98b2a5cad9618ab4
parentd22f67848ca1b5b34eb09b58c866a80eae3c7da1 (diff)
[3.0.x] Updated link to Celery.
Backport of 06c8565a4650b359bdfa59f9707eaa0d1dfd7223 from master
-rw-r--r--docs/topics/db/transactions.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt
index cebec3d7d1..167b95d01a 100644
--- a/docs/topics/db/transactions.txt
+++ b/docs/topics/db/transactions.txt
@@ -281,7 +281,7 @@ Sometimes you need to perform an action related to the current database
transaction, but only if the transaction successfully commits. Examples might
include a `Celery`_ task, an email notification, or a cache invalidation.
-.. _Celery: http://www.celeryproject.org/
+.. _Celery: https://pypi.org/project/celery/
Django provides the :func:`on_commit` function to register callback functions
that should be executed after a transaction is successfully committed: