#20892: Allow configuring the memcached Client with CACHES 'OPTIONS'
-------------------------------------+------------------------------------
Reporter: alex@… | Owner: edmorley
Type: New feature | Status: assigned
Component: Core (Cache system) | Version: 1.5
Severity: Normal | Resolution:
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 edmorley):
* status: new => assigned
* needs_better_patch: 1 => 0
* owner: nobody => edmorley
* cc: emorley@… (added)
Comment:
I've opened a new PR, which takes a slightly different approach:
* The contents of `OPTIONS` is now passed directly to the client
constructor
* For pylibmc, behaviors are now passed inside the `behaviors` key within
`OPTIONS`, rather than as top-level properties of `OPTIONS`. The old
behavior is still supported for now, but generates deprecation warnings.
Discussion of alternative approaches (on the old PR):
https://github.com/django/django/pull/6233#issuecomment-192459369
The new PR:
https://github.com/django/django/pull/7160
--
Ticket URL: <https://code.djangoproject.com/ticket/20892#comment:19>
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.cf69100ad1217e3ed70f89e9aa070c1d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
