Re: [openstack-dev] Selecting more carefully our dependencies

2014-05-31 Thread Thomas Goirand
On 05/30/2014 03:22 PM, Chmouel Boudjnah wrote: > > On Thu, May 29, 2014 at 11:25 AM, Thomas Goirand > wrote: > > So I'm wondering: are we being careful enough when selecting > dependencies? In this case, I think we haven't, and I would recommend > against usi

Re: [openstack-dev] Selecting more carefully our dependencies

2014-05-30 Thread Thierry Carrez
Thomas Goirand wrote: > So I'm wondering: are we being careful enough when selecting > dependencies? In this case, I think we haven't, and I would recommend > against using wrapt. Not only because it embeds six.py, but because > upstream looks uncooperative, and bound to its own use cases. Propose

Re: [openstack-dev] Selecting more carefully our dependencies

2014-05-30 Thread Chmouel Boudjnah
On Thu, May 29, 2014 at 11:25 AM, Thomas Goirand wrote: > So I'm wondering: are we being careful enough when selecting > dependencies? In this case, I think we haven't, and I would recommend > against using wrapt. Not only because it embeds six.py, but because > upstream looks uncooperative, and

Re: [openstack-dev] Selecting more carefully our dependencies

2014-05-29 Thread Thomas Goirand
On 05/29/2014 05:25 PM, Thomas Goirand wrote: > Hi everyone, > > Recently, wrapt was added as a dependency. The Python module suffers > from obvious design issues, like for example: > - Lack of Python 3.4 support > - Broken with Python 3.2 > - Upstream sources in "src" instead of "wrapt" so then r

Re: [openstack-dev] Selecting more carefully our dependencies

2014-05-29 Thread Joshua Harlow
n Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, May 29, 2014 at 2:25 AM To: "OpenStack Development Mailing List (not for usage questions)" Subject: [openstack-dev] Selecting more carefully our dependencies >Hi everyone, > >Recen

[openstack-dev] Selecting more carefully our dependencies

2014-05-29 Thread Thomas Goirand
Hi everyone, Recently, wrapt was added as a dependency. The Python module suffers from obvious design issues, like for example: - Lack of Python 3.4 support - Broken with Python 3.2 - Upstream sources in "src" instead of "wrapt" so then running py.test doesn't work unless you do "ln -s src wrapt",