There is issue that, even if coloredlogs is installed on a custom (app) logger (via install(level=logging.DEBUG, logger=my_app_logger), it seems to interfere with log level of the root logger itself (reduced to DEBUGtoo); This in turn causes output from all other libraries and dependencies to show up in your logs!
I checked and confirmed this. Before calling install, I set log level on the root logger to ERROR or 40, but after installroot logger's log level is decreased to DEBUG or 10(the level which I use for my own app's log output); Then, logs from all other libraries (which before using install had been "silenced") start to pollute the landscape (stdout)!
A temporary fix seems to be setting the log level on the root logger again after intalling coloredlogs
Thanks for coloredlogs.
There is issue that, even if coloredlogs is installed on a custom (app) logger (via
install(level=logging.DEBUG, logger=my_app_logger), it seems to interfere withlog levelof the root logger itself (reduced toDEBUGtoo); This in turn causes output from all other libraries and dependencies to show up in your logs!I checked and confirmed this. Before calling
install, I set log level on the root logger toERROR or 40, but afterinstallroot logger's log level is decreased toDEBUG or 10(the level which I use for my own app's log output); Then, logs from all other libraries (which before using install had been "silenced") start to pollute the landscape (stdout)!A temporary fix seems to be setting the log level on the root logger again after intalling coloredlogs