[openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)
morgan.fainberg at gmail.com
Fri Jul 17 12:36:07 UTC 2015
> On Jul 17, 2015, at 04:36, Victor Stinner <vstinner at redhat.com> wrote:
> Le 16/07/2015 22:28, Thomas Goirand a écrit :
>> IMO, we should, for the Liberty release, get rid of:
>> - suds & suds-jurko
> suds was replaced with suds-jurko (in oslo.vmware, cinder, nova): I kicked suds off of global requirements.
>> - memcached (in the favor of pymemcache)
> As I wrote, I may fork python-memcached. It's just not in my priority list right now.
Pymemcached would be my choice instead of forking this project. However, pymemcached is missing multiple server connections and key/hash ring capabilities (afaik there is a pull request/active development to cover those gaps).
> FYI some colleagues just forked python-ldap in https://github.com/pyldap/pyldap/ to add Python 3 support. Stay tuned ;-)
I highly recommend contributing to the ldap3 project instead of continuing the python-ldap work. Ldap3 is (imho) a much better design and really (if anything) simply lacks a compatibility layer.
Keystone will be moving to ldap3 (regardless of the compat module) either this cycle or next.
>> - mysqldb (this has been discussed at large already)
> MySQL-Python was replaced with PyMySQL in almost all projects, no? Even nova is now using PyMySQL ;-)
>> - cliff-tablib and tablib (not ported to Py3, used only for testing)
> tablib works on Python 3, but it has a strange way of using dependencies. You can try to remove tablib/packages/markup.py when building the package for Python 3 and it should just work.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev