#20892: Allow configuring the memcached Client with CACHES 'OPTIONS'
-------------------------------------+------------------------------------
Reporter: alex@… | Owner: edmorley
Type: New feature | Status: closed
Component: Core (Cache system) | Version: 1.5
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"65ec8fa8ca56a5378345375e1079025c96d0b833" 65ec8fa]:
{{{
#!CommitTicketReference repository=""
revision="65ec8fa8ca56a5378345375e1079025c96d0b833"
Fixed #20892 -- Allowed configuring memcached client using OPTIONS.
Previously, the MemcachedCache backend ignored `OPTIONS` and
PyLibMCCache used them to set pylibmc behaviors. Both backends now
pass `OPTIONS` as keyword arguments to the client constructors.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/20892#comment:21>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.96789b5f63f301a0c591997ab9159c1a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
