On 14 March 2016 at 15:27, Sam Ruby wrote:
> On Mon, Mar 14, 2016 at 11:09 AM, sebb wrote:
>> On 14 March 2016 at 14:22, Sam Ruby wrote:
>>> On Mon, Mar 14, 2016 at 10:10 AM, sebb wrote:
On 14 March 2016 at 12:55, sebb wrote:
> It would be useful to be able to initialise the default l
On Mon, Mar 14, 2016 at 11:09 AM, sebb wrote:
> On 14 March 2016 at 14:22, Sam Ruby wrote:
>> On Mon, Mar 14, 2016 at 10:10 AM, sebb wrote:
>>> On 14 March 2016 at 12:55, sebb wrote:
It would be useful to be able to initialise the default log level but
still allow CLI over-ride.
On 14 March 2016 at 14:22, Sam Ruby wrote:
> On Mon, Mar 14, 2016 at 10:10 AM, sebb wrote:
>> On 14 March 2016 at 12:55, sebb wrote:
>>> It would be useful to be able to initialise the default log level but
>>> still allow CLI over-ride.
>>>
>>> I've found a hacky fix:
>>>
>>> Wunderbar.log_leve
On Mon, Mar 14, 2016 at 10:10 AM, sebb wrote:
> On 14 March 2016 at 12:55, sebb wrote:
>> It would be useful to be able to initialise the default log level but
>> still allow CLI over-ride.
>>
>> I've found a hacky fix:
>>
>> Wunderbar.log_level = 'info' unless Wunderbar.log_level == 'debug' #
>>
On 14 March 2016 at 12:55, sebb wrote:
> It would be useful to be able to initialise the default log level but
> still allow CLI over-ride.
>
> I've found a hacky fix:
>
> Wunderbar.log_level = 'info' unless Wunderbar.log_level == 'debug' #
> don't override command-line level
>
> however that reli
It would be useful to be able to initialise the default log level but
still allow CLI over-ride.
I've found a hacky fix:
Wunderbar.log_level = 'info' unless Wunderbar.log_level == 'debug' #
don't override command-line level
however that relies on knowing that debug (and only debug) is more
verbo
