Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-26 Thread Davanum Srinivas
FYI, * Solly Ross graciously cut a websockify release: https://review.openstack.org/#/c/205492/ * Sean Reifschneider just released a python-memcached with haypo's py34 patch: https://review.openstack.org/#/c/205851/ Thanks, dims On Fri, Jul 17, 2015 at 7:53 PM, Dave Walker em...@daviey.com

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Joshua Harlow
Sounds good to me, +1 I know that some of the oslo core (I've done a little) and others (victor does a-lot of it) have been taking over this duty already but some kind of miniature group that has this a main goal would be cool to. -Josh Davanum Srinivas wrote: Thierry, +1 from me. We

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Joshua Harlow
Victor Stinner 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)

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Thierry Carrez
Davanum Srinivas wrote: Sounds like a great idea Thierry! Any concrete deliverables you have in mind for this group? I don't think that team would use a specific repository. More like agree on a set of objectives to reach in a given cycle, like the list Thomas came up with. If one ends up being

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Morgan Fainberg
On Jul 17, 2015, at 04:36, Victor Stinner vstin...@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

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Davanum Srinivas
Thierry, +1 from me. We could just use a wiki to track work or upstream PR/reviews for now. -- dims On Fri, Jul 17, 2015 at 7:40 AM, Thierry Carrez thie...@openstack.org wrote: Davanum Srinivas wrote: Sounds like a great idea Thierry! Any concrete deliverables you have in mind for this

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Joshua Harlow
Morgan Fainberg wrote: On Jul 17, 2015, at 04:36, Victor Stinnervstin...@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

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Victor Stinner
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

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Davanum Srinivas
Sounds like a great idea Thierry! Any concrete deliverables you have in mind for this group? thanks, dims On Fri, Jul 17, 2015 at 6:07 AM, Thierry Carrez thie...@openstack.org wrote: Thomas Goirand wrote: IMO, we should, for the Liberty release, get rid of: - suds suds-jurko - memcached (in

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Thierry Carrez
Thomas Goirand wrote: IMO, we should, for the Liberty release, get rid of: - suds suds-jurko - memcached (in the favor of pymemcache) - mysqldb (this has been discussed at large already) - cliff-tablib and tablib (not ported to Py3, used only for testing) I feel like there is an opportunity

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Joshua Harlow
Well we already have a debtcollector[1] library, It serves similar purposes for actively maintained libraries (not dead/abandoned ones), So how about a group named 'the debtcollectors' [1] http://docs.openstack.org/developer/debtcollector/ Thierry Carrez wrote: Joshua Harlow wrote: Sounds

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Davanum Srinivas
Josh, How about a defibrillators :) or a phoenix reference! but seriously, we probably need some official-ish name like Community outreach or Ecosystem curators.. Thanks, dims On Fri, Jul 17, 2015 at 1:24 PM, Joshua Harlow harlo...@outlook.com wrote: Well we already have a debtcollector[1]

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-17 Thread Dave Walker
On 17 Jul 2015 1:38 pm, Morgan Fainberg morgan.fainb...@gmail.com wrote: On Jul 17, 2015, at 04:36, Victor Stinner vstin...@redhat.com wrote: SNIP FYI some colleagues just forked python-ldap in https://github.com/pyldap/pyldap/ to add Python 3 support. Stay tuned ;-) I highly recommend

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-16 Thread Doug Hellmann
Excerpts from Davanum Srinivas (dims)'s message of 2015-07-16 11:00:33 -0400: Hi all, I ended up here: https://github.com/linsomniac/python-memcached/issues/54 https://github.com/linsomniac/python-memcached/pull/67 while chasing a keystone py34 CI problem since memcached is running in

[openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-16 Thread Davanum Srinivas
Hi all, I ended up here: https://github.com/linsomniac/python-memcached/issues/54 https://github.com/linsomniac/python-memcached/pull/67 while chasing a keystone py34 CI problem since memcached is running in our CI VM: https://review.openstack.org/#/c/177661/ and got word from @zigo that this

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-16 Thread Victor Stinner
Hi, Le 16/07/2015 17:00, Davanum Srinivas a écrit : I ended up here: https://github.com/linsomniac/python-memcached/issues/54 https://github.com/linsomniac/python-memcached/pull/67 Oh, that's my pull request :-) Multiple peoples asked to merge my pull request, and I pinged explicitly the

Re: [openstack-dev] [all] Non-responsive upstream libraries (python34 specifically)

2015-07-16 Thread Thomas Goirand
On 07/16/2015 05:19 PM, Doug Hellmann wrote: Excerpts from Davanum Srinivas (dims)'s message of 2015-07-16 11:00:33 -0400: Hi all, I ended up here: https://github.com/linsomniac/python-memcached/issues/54 https://github.com/linsomniac/python-memcached/pull/67 while chasing a keystone py34