DISCUSSION: Logger .. test, ideas and incorporating a global logging class

[carsten-forty2]

Several log levels would be nice: Quiet, Info, Debug, Insane, Warn, Error

ALL! output inside pygimli should write into the logger.

./appX --verbose should set the logger to 'Info'
./appX --debug should set pg.setDebug() and the logger to 'Debug'

-Quiet for default or gui mode, Warn=off, Error=on

-Insane only for internal use

Is there a way to extract the output from the logger for futher GUI usage?
Is it distinguishable between cout cerr?

check:
logging package

[florian-wagner]

I like the idea 👍 The std logging module seems to provide everything required but is the C++ part able to talk to the logger?

[carsten-forty2]

Agree https://docs.python.org/3/howto/logging.html#logging-basic-tutorial seems to be reliable for this task.

I let it open until I found a way to call this from the core, but we should start to use this logging instead of print() whenever possible.

[carsten-forty2]

made a little progress .. C++ part can now talk to the logger .. we now only need to define some defaults behavior

[halbmy]

great!
will not void log(...) in gimli.cpp override override pg.log (logarithm)?

[carsten-forty2]

hmm .. good point .. did not yet tested it but should be no problem since log(logging) needs two args (int, str) and log(logarithm) only can handle one arg (float|iterable)

[carsten-forty2]

Add new tests and syntax suggestions .. still work in progress and discussion is appreciated.

import pygimli as pg
# library related logs with 
pg.logger.info(msg)
pg.logger.warn(msg)
# core related logs (should not used from python code
pg.log(Info, msg) 

See testing/test_logger.py for more examples.

[carsten-forty2]

new logger syntax to try .. less to type

pg.info(msg) pg.warn(msg) pg.error(msg) pg.debug(msg) pg.critical(msg)

[florian-wagner]

Nice, this is handy and not more effort than a print statement. 👍