Opened 3 years ago
Closed 3 years ago
#34314 closed Uncategorized (invalid)
pymemcached noreply support
| Reported by: | Matej Spiller Muys | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Cache system) | Version: | 4.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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]:
Change History (1)
comment:1 by , 3 years ago
| Component: | Uncategorized → Core (Cache system) |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
You can set
default_noreplyin OPTIONS to usenoreplyby default, see docs.