I believe we have smth like that in our config module... indeed checkout ```getboolean``` which relies on following dictionary defined in ConfigParser:
```
In [2]: cfg._boolean_states
Out[2]: 
{'0': False,
 '1': True,
 'false': False,
 'no': False,
 'off': False,
 'on': True,
 'true': True,
 'yes': True}
```

ideally we better stay consistent with it, thus could RF our ConfigManager to have a classmethod ```to_bool(v)``` which would absorb that logic to be reused for config and here instead of yesno2bool?