None typage for unset config object lead to unexpected behavior

[dmp42]

cfg.get('whatever') will return None.

Parts of the code expect an unset value to default to False, and obviously False is not None.

[wking]

On Fri, Jun 13, 2014 at 10:15:54AM -0700, Mangled Deutz wrote:

Parts of the code expect an unset value to default to False, and
obviously False is not None.

In situations like this, I think it's usually best to use:

if myvar:

or:

if not myvar:

instead of the stricter:

if myvar == True:

or:

if myvar == False:

Obviously, that's if the “unset” None should be defaulting to False,
which is also usually the case for me.

[dmp42]

I believe this was fixed by #444 with a more logic config evaluation system.