Clear logging handler when initializing the logger #529
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch clears the root logging handlers when initializing the logger.
This might be considered a quickfix. The root problem is that the configuration might be loaded twice when starting up:
__main__.py
callsconfig.update_configuration
explicitly.The result is that the list of root logging handlers contains duplicate entries. Each line is thus logged twice.
Since the config can be loaded lazily, one might remove the explicit call in
__main__.py
. However, my reasoning for this approach was that resetting the logger handlers during initialization makes sense anyway.