Re: [openstack-dev] [oslo] Why are we continuing to add new namespaced oslo libs?

2015-01-30 Thread Thomas Goirand
On 01/29/2015 05:24 PM, Doug Hellmann wrote: On Thu, Jan 29, 2015, at 11:03 AM, Thomas Goirand wrote: On 01/24/2015 02:01 AM, Doug Hellmann wrote: On Fri, Jan 23, 2015, at 07:48 PM, Thomas Goirand wrote: Hi, I've just noticed that oslo.log made it to global-requirements.txt 9 days

Re: [openstack-dev] [oslo] Why are we continuing to add new namespaced oslo libs?

2015-01-29 Thread Doug Hellmann
On Thu, Jan 29, 2015, at 11:03 AM, Thomas Goirand wrote: On 01/24/2015 02:01 AM, Doug Hellmann wrote: On Fri, Jan 23, 2015, at 07:48 PM, Thomas Goirand wrote: Hi, I've just noticed that oslo.log made it to global-requirements.txt 9 days ago. How come are we still adding some

Re: [openstack-dev] [oslo] Why are we continuing to add new namespaced oslo libs?

2015-01-29 Thread Julien Danjou
On Thu, Jan 29 2015, Thomas Goirand wrote: Hi Thomas, The Debian policy is that Python module packages should be named after the import statement in a source file. Meaning that if we do: import oslo_db then the package should be called python-oslo-db. This means that I will have to

Re: [openstack-dev] [oslo] Why are we continuing to add new namespaced oslo libs?

2015-01-29 Thread Thierry Carrez
Julien Danjou wrote: On Thu, Jan 29 2015, Thomas Goirand wrote: Hi Thomas, The Debian policy is that Python module packages should be named after the import statement in a source file. Meaning that if we do: import oslo_db then the package should be called python-oslo-db. This means

Re: [openstack-dev] [oslo] Why are we continuing to add new namespaced oslo libs?

2015-01-29 Thread Joshua Harlow
Just something to note; anvil has never ran had issues with this (afaik). It seems fairly easy to have a mapping/algorithm/other... that is used imho (and this is just what anvil has); I don't recall that the number of problems with weird names has been any real issue when building rpms...

Re: [openstack-dev] [oslo] Why are we continuing to add new namespaced oslo libs?

2015-01-29 Thread Thomas Goirand
On 01/24/2015 02:01 AM, Doug Hellmann wrote: On Fri, Jan 23, 2015, at 07:48 PM, Thomas Goirand wrote: Hi, I've just noticed that oslo.log made it to global-requirements.txt 9 days ago. How come are we still adding some name.spaced oslo libs? Wasn't the outcome of the discussion in Paris

Re: [openstack-dev] [oslo] Why are we continuing to add new namespaced oslo libs?

2015-01-23 Thread Louis Taylor
On Sat, Jan 24, 2015 at 01:48:32AM +0100, Thomas Goirand wrote: I've just noticed that oslo.log made it to global-requirements.txt 9 days ago. How come are we still adding some name.spaced oslo libs? Wasn't the outcome of the discussion in Paris that we shouldn't do that anymore, and that we

Re: [openstack-dev] [oslo] Why are we continuing to add new namespaced oslo libs?

2015-01-23 Thread Doug Hellmann
On Fri, Jan 23, 2015, at 07:48 PM, Thomas Goirand wrote: Hi, I've just noticed that oslo.log made it to global-requirements.txt 9 days ago. How come are we still adding some name.spaced oslo libs? Wasn't the outcome of the discussion in Paris that we shouldn't do that anymore, and that we

[openstack-dev] [oslo] Why are we continuing to add new namespaced oslo libs?

2015-01-23 Thread Thomas Goirand
Hi, I've just noticed that oslo.log made it to global-requirements.txt 9 days ago. How come are we still adding some name.spaced oslo libs? Wasn't the outcome of the discussion in Paris that we shouldn't do that anymore, and that we should be using oslo-log instead of oslo.log? Is three