Be considerate of logging as library code - #4
Merged
Conversation
je-cook
force-pushed
the
je-cook/considerate_logging
branch
from
August 27, 2025 09:38
7e0f7b0 to
b0eead9
Compare
hsaunders1904
approved these changes
Aug 27, 2025
hsaunders1904
left a comment
hsaunders1904
left a comment
Contributor
There was a problem hiding this comment.
Looks fine to me 👍
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
By setting up basicConfig downstream packages get bombarded with logging. This only sets up a stderr handler at WARNING which is the only logging we have currently