On Wed, Nov 13, 2013 at 4:13 AM, Roman Podoliaka wrote:
> Hi Flavio,
>
> Thanks for sharing this! I attended that session, but haven't seen the
> corresponding blueprint before.
>
> Nevertheless, I'm not sure that implementing this entirely solves the
> original problem. Removing import side-effec
Hi Flavio,
Thanks for sharing this! I attended that session, but haven't seen the
corresponding blueprint before.
Nevertheless, I'm not sure that implementing this entirely solves the
original problem. Removing import side-effects is definitely the right
thing to do, but options will be eventuall
On 12/11/13 17:21 +0200, Roman Podoliaka wrote:
Hi all,
Currently, many modules from openstack.common package register
oslo.config options. And this is completely OK while these modules are
copied to target projects using update.py script.
But consider the situation, when we decide to split a n
Hi all,
Currently, many modules from openstack.common package register
oslo.config options. And this is completely OK while these modules are
copied to target projects using update.py script.
But consider the situation, when we decide to split a new library from
oslo-incubator - oslo.spam - and t
