#9180: Low-level cache interface incorrectly tries to typecast bytestring
-----------------------------------+----------------------------------------
Reporter: p | Owner: nobody
Status: new | Milestone:
Component: Cache system | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Comment (by AdamG):
See also #5589. I would greatly prefer the `raw` kwarg, as using the
1-tuple solution would mean that Python pickles are actually being cached,
which would mean that the cache can only be primed by Python code - and
when using something like memcached, that's not always the case. For
example, I often put output from imagemagick into memcached; right now,
that's innaccessible from `django.core.cache.cache` due to this issue.
--
Ticket URL: <http://code.djangoproject.com/ticket/9180#comment:2>
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 django-updates@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
