Steve, Couple of points:
* We can add pylibmc to g-r and phase out python-memcached over a time period. * If folks are using python-memcached, we should switch then over to oslo.cache, then only oslo.cache will reference either python-memcached or pylibmc which will make the situation easier to handle. Thanks, Dims On Fri, May 13, 2016 at 4:14 AM, Steve Martinelli <s.martine...@gmail.com> 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 codesearch) > > 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 > python-memcached? > - Will buy-in from all projects be necessary to proceed for any single > project? > > Open issues like this: > https://github.com/linsomniac/python-memcached/issues/94 make me sad. > > stevemar > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Davanum Srinivas :: https://twitter.com/dims __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
