-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
bpo-45635: refactor print_exception_recursive into smaller functions to standardize error handling #30015
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
Merged
Merged
bpo-45635: refactor print_exception_recursive into smaller functions to standardize error handling #30015
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
fec85a6
bpo-45635: refactor print_exception_recursive into smaller functions …
iritkatriel 5d68eb5
extract print_exception_seen_lookup
iritkatriel e0d0f8a
Apply suggestions from code review
iritkatriel a386833
a couple more review comments
iritkatriel 5dc1936
newline
iritkatriel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't it be clearer to just return if we don't need to do anything else? Actually, seeing that
err
is only set twice, I wonder if it could be worth it to just inline the error handling (PyErr_Clear()
) and removeerr
🤔 Nitpicking 😎There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will happen, once this function stops swallowing errors (that's a behaviour change rather than a refactor). Right now we have the PyErr_Clear() at the end.