#32076: Adding async methods to BaseCache
-------------------------------------+-------------------------------------
Reporter: Andrew Chen Wang | Owner: nobody
Type: New feature | Status: closed
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution: needsinfo
Keywords: cache | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* cc: Andrew Godwin (added)
* status: new => closed
* resolution: => needsinfo
* needs_tests: 1 => 0
Comment:
It looks that your proposition doesn't match with accepted
[https://github.com/django/deps/blob/master/accepted/0009-async.rst#caching
DEP-9]:
> Default implementations of these that just call the existing API via
sync_to_async will be provided in BaseCache.
Moreover, I'm not sure if we want to release any partial solution without
a real async support in caching. DEP 9 suggests that a separate DEP is
required:
> Some features, like templating and cache backends, will need their own
separate DEPs and research to be fully async. This DEP mostly focuses on
the HTTP-middleware-view flow and the ORM.
Initially closing as needsinfo. Andrew, Can I ask for your opinion?
--
Ticket URL: <https://code.djangoproject.com/ticket/32076#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/074.288c94a8f59b08c73c0be848b2a08a29%40djangoproject.com.
