Re: [openstack-dev] When will we stop adding new Python modules to requirements

2013-09-16 Thread Matthias Runge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16/09/13 17:51, Michael Basnight wrote: >> Currently, just the docs refer to reddwarf, resulting in build >> issues when building docs. >> > > Whew! Ill fix it anyway. Thx fro pointing it out. > Awesome, Michael. Very much appreciated! Matthias

Re: [openstack-dev] When will we stop adding new Python modules to requirements

2013-09-16 Thread Michael Basnight
On Sep 16, 2013, at 9:05 AM, Matthias Runge wrote: > Signed PGP part > On 16/09/13 17:51, Michael Basnight wrote: > > >> Currently, just the docs refer to reddwarf, resulting in build > >> issues when building docs. > >> > > > > Whew! Ill fix it anyway. Thx fro pointing it out. > > > Awesome,

Re: [openstack-dev] When will we stop adding new Python modules to requirements

2013-09-16 Thread Michael Basnight
On Sep 16, 2013, at 12:24 AM, Matthias Runge wrote: > On 16/09/13 05:30, Monty Taylor wrote: >> >> >> On 09/15/2013 01:47 PM, Alex Gaynor wrote: >>> Falcon was included as a result of Marconi moving from stackforge to >>> being incubated. sphinxcontrib-programoutput doesn't appear to have been

Re: [openstack-dev] When will we stop adding new Python modules to requirements

2013-09-16 Thread Matthias Runge
On 16/09/13 17:36, Michael Basnight wrote: >> >> Not to forget python-troveclient, which is currently a hard >> requirement for Horizon. >> >> During the review for python-troveclient, it was discovered, >> troveclient still references reddwarfclient (in docs/source). > > Are you saying it refe

Re: [openstack-dev] When will we stop adding new Python modules to requirements

2013-09-16 Thread Michael Basnight
On Sep 16, 2013, at 8:42 AM, Matthias Runge wrote: > On 16/09/13 17:36, Michael Basnight wrote: > >>> >>> Not to forget python-troveclient, which is currently a hard >>> requirement for Horizon. >>> >>> During the review for python-troveclient, it was discovered, >>> troveclient still referenc

Re: [openstack-dev] When will we stop adding new Python modules to requirements

2013-09-16 Thread Matthias Runge
On 16/09/13 05:30, Monty Taylor wrote: > > > On 09/15/2013 01:47 PM, Alex Gaynor wrote: >> Falcon was included as a result of Marconi moving from stackforge to >> being incubated. sphinxcontrib-programoutput doesn't appear to have been >> added at all, it's still under >> review: https://review.o

Re: [openstack-dev] When will we stop adding new Python modules to requirements

2013-09-15 Thread Monty Taylor
On 09/15/2013 01:47 PM, Alex Gaynor wrote: > Falcon was included as a result of Marconi moving from stackforge to > being incubated. sphinxcontrib-programoutput doesn't appear to have been > added at all, it's still under > review: https://review.openstack.org/#/c/46325/ I agree with Alex and Mo

Re: [openstack-dev] When will we stop adding new Python modules to requirements

2013-09-15 Thread Alex Gaynor
Falcon was included as a result of Marconi moving from stackforge to being incubated. sphinxcontrib-programoutput doesn't appear to have been added at all, it's still under review: https://review.openstack.org/#/c/46325/ Alex On Sun, Sep 15, 2013 at 11:39 AM, Morgan Fainberg wrote: > Thomas, >

Re: [openstack-dev] When will we stop adding new Python modules to requirements

2013-09-15 Thread Morgan Fainberg
Thomas, A couple if those appear to be managed by the OpenStack community (e.g. diskimage-builder), which likely should be included in either case. I would say if it is covered under the OpenStack proper list of git repos (e.g. https://github.com/openstack ) it should likely be included for packa

[openstack-dev] When will we stop adding new Python modules to requirements

2013-09-15 Thread Thomas Goirand
Hi, Short version: the global-requirements.txt should be frozen asap because otherwise, packages wont be ready. Longer version: I'm getting worried that, even after Havana b3 is released, we are still getting some new Python modules added to the requirements repository. In Debian, every new pac