#32749: PyMemcacheCache uses default_noreply=False although pymemcache
recommends
to set to True
-------------------------------------+-------------------------------------
Reporter: yakirsudry | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.2
Severity: Normal | Resolution:
Keywords: pymemcache | Triage Stage:
PyMemcacheCache | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
[https://github.com/django/django/pull/13310#discussion_r632986159
Parallel conversation on Github]. Nick mentioned that it was done to make
the backend a drop in replacement with other MC backends but I'm curious
to see if any tests fail without this override. At the least we should
mention in the docs that these defaults are set for the `pymemcache`
backend as `django-pymemcache` doesn't behave this way.
--
Ticket URL: <https://code.djangoproject.com/ticket/32749#comment:1>
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.01d69e072ba284a8978b811e17cecd06%40djangoproject.com.
