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.
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
Add support to testing.RaisesGroup for catching unwrapped exceptions #2989
Add support to testing.RaisesGroup for catching unwrapped exceptions #2989
Changes from 15 commits
4497b3d
62c0ea0
f50f808
f5c755f
cf64533
38c950b
c506a89
0bff4e6
62246f1
3a56911
cc5d980
1a89cd7
5af79ac
8f72967
ff3e5fc
2df4c1c
c4dbb78
b0d3408
36e757a
5179221
ff5d4eb
8b7aefc
2183e70
8c3f1f6
f736120
0c7591a
553df3d
04636ac
6f9a8a1
6ef442b
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.
Why aren't we using our deprecation utils in this case? Cause those would have the version this was deprecated in which is useful information.
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.
(If it's because they don't warn with something derived from
DeprecationWarning
that makes sense. Maybe add a kwarg towarn_deprecated
?)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.
mostly just me being confused about the existence of
TrioDeprecationWarning
(hence #2992). One weird part withwarn_deprecated
is you have to know what the next version bump will be, but I'm guessing I should mark it as0.25.1
.But I also don't think this one is worthy of an official extended period of supporting it, it's a trivial change to use
flatten_subgroups=True
instead and this is explicitly a temporary helper until it's merged into pytest, so it's barely worth having a DeprecationWarning at all. It's not used at runtime either, so it can only break tests. But I guessTrioDeprecationWarning
doesn't have an explicit promise of how long it will be kept deprecated anyhow