On 04/23/2015 04:24 PM, Victor Stinner wrote:
Also, on the Python 3 topic, there's still a big issue with memcached
(aka: python-memcache).
Oh, thanks Thomas for the reminder. I just sent a pull request to port
python-memcached to Python 3:
https://github.com/linsomniac/python-memcached/pull/67
Cool! I'll try it, apply the patch to the version 1.54, and upload to
Debian, if this works well.
I don't understand. I saw a lot of "Port to Python 3" fixes merged in 2014, and
these changes are now part of the release 1.54. Problem: running python-memcached tests
with tox fail on obvious Python 3 errors. Anyway, all tests now pass with my pull
request. The good news is that python-memcached looks to be actively developed.
Julien Danjou ported pymemcache to Python 3, another memcached client. He
suggests to use this one instead of python-memcached client.
pymemcache is much better in many ways, and switching to it shouldn't be
motivated only because of Python 3 compat.
It's blocking me from adding Python3 support to
keystoneclient, and as a consequence, to almost all of OpenStack.
python-keystoneclient announces a full Python 3 support with a voting Python 3 gate. I
just checked locally, "tox -e py34" pass.
The problem is that python-memcached miss in test dependencies and so
middleware tests using memcache are never run!
Victor
Yeah, memcached (aka: python-memcache in Debian) is said to be
"optional", but in reality, we really need it for the full Python 3
compatibility, otherwise that's bullshit (unless we're giving up on
using memcache completely?).
Cheers,
Thomas Goirand (zigo)
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
