#15815: Support memcached binary protocol in PyLibMCCache
-------------------------------------+------------------------------------
Reporter: mtigas | Owner:
Type: New feature | Status: new
Component: Core (Cache system) | Version: 1.3
Severity: Normal | Resolution:
Keywords: sprint2013 | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Comment (by edmorley):
In case this helps anyone working on this in the future, if you get test
failures running the Django pylibmc cache tests with binary mode enabled
in `test_zero_timeout()` - I believe it's due to a bug in older versions
of libmemcached-dev.
This appears to only affect `.set()` and not `.add()`, and only appears if
using binary mode. The bug means that a Django zero timeout (which is
converted to `-1` when passed to pylibmc) is ignored by libmemcached and
the key is in fact set after all.
Affected libmemcached versions include that running on Travis on their
Ubuntu precise images (which presuming they are using the official package
is http://packages.ubuntu.com/precise/libmemcached-dev). libmemcached-dev
1.0.8 on Ubuntu trusty works fine. I couldn't find a related bug or commit
on https://launchpad.net/libmemcached but Launchpad is pretty painful to
use so I may have just missed it.
--
Ticket URL: <https://code.djangoproject.com/ticket/15815#comment:16>
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/064.7a591bf62edccc89f077caa20384aa1c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.