#32749: PyMemcacheCache uses default_noreply=False although pymemcache
recommends
to set to True
-------------------------------------+-------------------------------------
Reporter: yakirsudry | Owner: nobody
Type: | Status: new
Cleanup/optimization |
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 Simon Charette):
Thanks for the extra details Nick.
In the light of these failures I think the only way we could get tests
passing/ensure the backend is fully functional without turning reply on
per client would be to 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.
Documenting to turn the option as is would simply break the backend so I'm
not convinced we should even do that anymore. Were you aware of that
yakirsudry?
--
Ticket URL: <https://code.djangoproject.com/ticket/32749#comment:4>
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/068.ab3e9876029fc445b949ccaa8df959f7%40djangoproject.com.
