Use exc_info keyword when logging an exception. #165
Closed
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.
An improvement of my older PR graphql-python/graphql-core#154 which replaced
sys.excepthook
with the logging module.Instead of manually formating the exception use the
exc_info
keyword to let the logging library handle the formatting, and properly set theexc_info
property of the log record.As @tlinhart pointed out in graphql-python/graphql-core#142 with the current implementation is difficult to filter which exceptions are logged.
This allows easier filtering of exceptions. Example: