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.
gh-103791: Make contextlib.suppress also act on exceptions within an ExceptionGroup #103792
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
gh-103791: Make contextlib.suppress also act on exceptions within an ExceptionGroup #103792
Changes from 5 commits
7bc3c15
08fa06c
be30df6
acf95f6
503d9f8
a43ffe4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Was there a specific reason to handle
ExceptionGroup
but notBaseExceptionGroup
?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.
I doubt it. Want to make a PR?
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 isn't ideal as it makes the exception group's own traceback include the
def __exit__(...)
frame. For example:in case of the newly added test.
This isn't a big problem because:
raise
of the original group is still included in the traceback because we used.split()
to create the new object.Ideally, we wouldn't need this. However, the API of
__exit__
makes it impossible to replace theExceptionGroup
instance with another one, whileExceptionGroup
itself makes its exceptions read-only.