Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Seems to interfere with logLevel of the root logger itself #117

Open
OnceUponATimeInAmerica opened this issue May 2, 2023 · 0 comments
Open

Comments

@OnceUponATimeInAmerica
Copy link

OnceUponATimeInAmerica commented May 2, 2023

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 with log level of the root logger itself (reduced to DEBUG too); 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 install root 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant