[Django] #34314: pymemcached noreply support
Django
-----------------------------------------+------------------------
Reporter: matejsp | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 4.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
Memcache supports noreply flag on set call (cas, set, set_many).
It would be beneficial to be able to set noreply flag on each call.
{{{
def set(
self,
key: Key,
value: Any,
expire: int = 0,
noreply: Optional[bool] = None,
flags: Optional[int] = None,
) -> Optional[bool]:
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34314>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: Matej Spiller Muys | Owner: nobody
Type: Uncategorized | Status: closed
Component: Core (Cache system) | Version: 4.1
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
* component: Uncategorized => Core (Cache system)
Comment:
You can set `default_noreply` in
[https://docs.djangoproject.com/en/stable/ref/settings/#std-setting-
CACHES-OPTIONS OPTIONS] to use `noreply` by default, see
[https://docs.djangoproject.com/en/stable/topics/cache/#memcached docs].
--
Ticket URL: <https://code.djangoproject.com/ticket/34314#comment:1>