#11675: [patch] Support new memcached wrapper pylibmc
------------------------------------------+---------------------------------
Reporter: pipp...@yahoo.co.jp | Owner: otherjacob
Status: assigned | Milestone: 1.3
Component: Cache system | Version: SVN
Resolution: | Keywords: cache pylibmc
memcached.py
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------------+---------------------------------
Comment (by gabrielhurley):
Replying to [comment:12 mmalone]:
> pylibmc raises pylibmc.NotFound if you incr/decr a key that doesn't
exist while the other Python clients raise ValueError. I'm pretty sure
this will break the Django memcache backend for incr/decr operations.
If necessary, it should be easy enough to catch that and then re-raise a
ValueError to be consistent. Django certainly does that to maintain
consistency in other places (such as for errors raised by different db
backends).
--
Ticket URL: <http://code.djangoproject.com/ticket/11675#comment:13>
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-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
