Double check console logging level & dynamic update change about sdna_gh HOT 3 CLOSED

Bug? The source code only says log_console_level = 'INFO'

from sdna_gh.

There's an extra handler (or output flow to sys.stderr) that the log levels in the options doesn't control - the format of the DEBUG messages is different when log_console_level > 'DEBUG'

from sdna_gh.

A couple of calls to logging.debug were creating a root logger at the level debug, with a console handler, to which messages were propagating from the sDNA_GH parent logger even when its level was higher than debug.

• logging.debug etc. calls have been replaced by logger.debug etc.
• propogate on parent logger has now been set to False by default (user toggleable), so the user can still create a root logger if they want to use sDNA_GH with some other GH Python code that also uses logging.
• A log file and file handler is only created now if log_file is a non-empty string.

from sdna_gh.