#6124: need a non-pickled locmem cache backend
-------------------------------------+-------------------------------------
Reporter: lukerl@… | Owner: nobody
Status: closed | Milestone:
Component: Cache | Version: SVN
system | Keywords: cache, locmem, pickle
Resolution: wontfix | Has patch: 1
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 |
Patch needs improvement: 1 |
-------------------------------------+-------------------------------------
Comment (by akaihola):
Replying to [comment:4 mtredinnick]:
> Since using external cache backends has been possible and
straightforwards for quite a while now (before Django 1.0, from memory),
there's no reason something like this has to be included. If anybody has a
reason to use a particular cache implementation, they can do just that and
reference it via a path in the settings. There's no need for it to be in
Django.
See [http://djangosnippets.org/snippets/2396/ django snippet #2396] for an
implementation of a non-pickling locmem external cache backend.
--
Ticket URL: <http://code.djangoproject.com/ticket/6124#comment:5>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.