DISCUSSION: Logger .. test, ideas and incorporating a global logging class about gimli HOT 8 CLOSED

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

from gimli.

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.

from gimli.

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

from gimli.

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

from gimli.

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)

from gimli.

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.

from gimli.

new logger syntax to try .. less to type

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

from gimli.

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

from gimli.