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
[PATCH] logging.config.fileConfig() compulsivly disable all existing loggers #47386
Comments
When using logging.config.fileConfig() in a large project, with several Attached is a sample patch that adds a new option You can see a simple example about the problem and solution here: without the patch, the output is: With the patch (and passing disable_existing_loggers=False to As one could expect when reading the logging module docs: |
Without the patch, but simply moving the fileConfig() call to above logger:DEBUG: log debug See |
The problem is you can't always do that call before using the loggers. In my case, I get the logging config file via command-line arguments Please reopen the bug, the actual solution is not flexible enough. |
Fixed checked into trunk. |
Thank you very much |
Here is a patch to add some documentation on the new fileConfig() |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: