[openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached
me at not.mn
Fri May 13 14:54:37 UTC 2016
On 13 May 2016, at 1:14, Steve Martinelli wrote:
> /me gets the ball rolling
> Just when python3 support for keystone was looking like a reality, we've
> hit another snag. Apparently there are several issues with python-memcached
> in py3, putting it simply: it loads, but doesn't actually work. I've
> included projects in the subject line that use python-memcached (based on
> Enter pylibmc; apparently it is (almost?) a drop-in replacement, performs
> better, and is more actively maintained.
> - Has anyone had success using python-memcached in py3?
> - Is anyone interested in using pylibmc in their project instead of
> - Will buy-in from all projects be necessary to proceed for any single
> Open issues like this:
> https://github.com/linsomniac/python-memcached/issues/94 make me sad.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
In Swift, we've got our own memcache client to get around some of the issues that were present in python-memcached at the time we needed it. Those issues may (or may not) be resolved now, but basically we've been very happy for years now with our own memcache client. It's drop-in compatible with python-memcached.
 https://github.com/openstack/swift/blob/master/swift/common/memcached.py (note the docstring at the top)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 801 bytes
Desc: OpenPGP digital signature
More information about the OpenStack-dev