From 8d2e3537874cef577f20c7b0e0208ff323592a23 Mon Sep 17 00:00:00 2001 From: sarina Date: Sun, 2 Feb 2025 11:57:24 -0500 Subject: [PATCH] docs: Mark OEP-3 as Accepted --- .../oep-0003-arch-async-tasks.rst | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/oeps/architectural-decisions/oep-0003-arch-async-tasks.rst b/oeps/architectural-decisions/oep-0003-arch-async-tasks.rst index f30fcb601..9f435c8aa 100644 --- a/oeps/architectural-decisions/oep-0003-arch-async-tasks.rst +++ b/oeps/architectural-decisions/oep-0003-arch-async-tasks.rst @@ -6,13 +6,13 @@ OEP-3: Asynchronous Task Management +---------------+-------------------------------------------+ | Title | Asynchronous Task Management | +---------------+-------------------------------------------+ -| Last-Modified | 2016-10-13 | +| Last-Modified | 2025-02-02 | +---------------+-------------------------------------------+ | Author | Jeremy Bowman | +---------------+-------------------------------------------+ | Arbiter | Eddie Fagin | +---------------+-------------------------------------------+ -| Status | Provisional | +| Status | Accepted | +---------------+-------------------------------------------+ | Type | Architecture | +---------------+-------------------------------------------+ @@ -27,6 +27,10 @@ results of various long-running tasks in a consistent manner. This system leverages existing libraries where practical and makes the development of new asynchronous tasks straightforward. +.. note:: + + This OEP served as the blueprint for `django-user-tasks `_. + Motivation ********** @@ -122,10 +126,10 @@ Database Schema =============== Celery provides a pretty full-featured and well understood platform for -running asynchronous tasks, but celery’s ``AsyncResult`` doesn’t store all +running asynchronous tasks, but celery's ``AsyncResult`` doesn't store all of the information we need for the desired features. Rather than try to -straddle the data we access across celery’s result backend and the MySQL -database, we’ll just store everything we need in database models and let +straddle the data we access across celery's result backend and the MySQL +database, we'll just store everything we need in database models and let celery manage and clean up its own result store as normal. Presented here is a suggested initial design for these models (they may be altered over time via migrations as more features are added). @@ -219,3 +223,8 @@ Backwards Compatibility Change History ************** + +2025-02-02 +========== +* Mark OEP as "Accepted", due to the implementation of the proposal in ``django-user-tasks`` +* `Pull request #672 `_