#32749: PyMemcacheCache uses default_noreply=False although pymemcache
recommends
to set to True
-------------------------------------+-------------------------------------
Reporter: yakirsudry | Owner: Nishant
Type: | Sagar
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 3.2
Severity: Normal | Resolution:
Keywords: pymemcache | Triage Stage: Accepted
PyMemcacheCache |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Johnson):
> We can add an admonition to state what options are being set by default
for pymemcache, but I don't feel that we need to change the behaviour.
+1 to this
> adjust all the methods that require a reply from MC to work properly to
explicitly pass noreply=False but I'm not sure there would be much benefit
from that.
Whether the reply is required depends on context... e.g. in the context of
tests, we check the status of operations, but user code may not care.
--
Ticket URL: <https://code.djangoproject.com/ticket/32749#comment:9>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.895432bc262e89c6746ac99217f0382f%40djangoproject.com.
