| 1 | | 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. |
| 2 | | |
| 3 | | 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. |
| 4 | | |
| 5 | | 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. |
| | 1 | <Removed incorrect comment about test failures in binary mode; turns out due to https://github.com/lericson/pylibmc/issues/202> |