do not configure logging on import, use named logger - #116
Open
dracador wants to merge 1 commit into
Open
Conversation
`convert_airtable.py` was configuring the logger for the root level, which clashes with other loggers that are properly configured via a logging dict, like how it's done normally in applications like django. In applications that configure their own logging this caused duplicated log lines and third-party output in seatable's format. It should be possible to toggle seatable_api logging on explicitly if it's needed. In general, libraries should only configure their own named logging space. See https://docs.python.org/3/howto/logging.html#configuring-logging-for-a-library
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
1 participant
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.
convert_airtable.pywas configuring the logger for the root level, which clashes with other loggers that are properly configured via a logging dict, like how it's done normally in applications like django.In applications that configure their own
logging this caused duplicated log lines and third-party output in seatable's format.
It should be possible to toggle seatable_api logging on explicitly if it's needed.
In general, libraries should only configure their own named logging space. See https://docs.python.org/3/howto/logging.html#configuring-logging-for-a-library