Excerpts from Mark McLoughlin's message of 2013-07-01 15:12:51 -0700:
On Mon, 2013-07-01 at 14:52 -0700, Clint Byrum wrote:
Last week I went to use oslo.config in a utility I am writing called
os-collect-config[1]...
While running unit tests on the main() method that is used for the CLI,
On Tue, 2013-07-02 at 00:24 -0700, Clint Byrum wrote:
Excerpts from Mark McLoughlin's message of 2013-07-01 15:12:51 -0700:
On Mon, 2013-07-01 at 14:52 -0700, Clint Byrum wrote:
Last week I went to use oslo.config in a utility I am writing called
os-collect-config[1]...
While
On 2013-07-01 15:10:26 -0700 (-0700), Mark Washenberger wrote:
[...]
The talk about permanence confuses me, unless we mean that more
permanent values are overridden by less permanent ones.
[...]
I think the permanence counter argument (which I don't agree with,
just recounting it for
Last week I went to use oslo.config in a utility I am writing called
os-collect-config[1]...
While running unit tests on the main() method that is used for the CLI,
I was surprised to find that my unit tests were picking up values from
a config file I had created just as a test. The tests can be
I think I had a different takeaway from that thread. My understanding was
that people were agreeing with you that CLI args *should* have highest
precedence and override everything else.
The talk about permanence confuses me, unless we mean that more permanent
values are overridden by less
On Mon, Jul 01, 2013, Clint Byrum cl...@fewbar.com wrote:
I am writing today to challenge that notion, and also to suggest that even
if that is the case, it is inappropriate to have oslo.config operate in
such a profoundly different manner than basically any other config library
or system
