Corrected a missmatch between the verbose environnement flag and read value

[egguy]

When setting the environment flag gverbose to True or False, there is no change.

The problem stems from this line:

if os.getenv('gverbose') != None : self.verbose = self.getenv('verbose')

If the env var gverbose is detected, it reads the env var verbose, but verbose is not set, so the verbose mode stays False.

If you set both the env var to :

gverbose=True
verbose=True

It starts to work

This patch corrects this problem Tested after the patch, you only need to set gverbose for the verbose logging to work.

[johanmeijer]

Thanks will merge this soon.

[rany2]

@johanmeijer I realized that this method of manually specifying environment key is so error-prone. In my fork I have this process automated via a custom configparser with option of specifying a custom env key in case of conflict (like influxdb/mqtt username/pass) https://github.com/rany2/grott/blob/master/grottconf.py#L25-L66

[johanmeijer]

I changed the error according the gverbose manually.

I like the idea of the automatic generation off the environmental variables and will pick to up in a next release (needs some more test work from my side).