-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
display single contained exception in excgroups in test summary #12975
Open
jakkdl
wants to merge
6
commits into
pytest-dev:main
Choose a base branch
from
jakkdl:short_info_excgroup
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
psf-chronographer
bot
added
the
bot:chronographer:provided
(automation) changelog entry is part of PR
label
Nov 18, 2024
Zac-HD
reviewed
Nov 19, 2024
Comment on lines
+593
to
+595
def _get_single_subexc( | ||
eg: BaseExceptionGroup[BaseException], | ||
) -> BaseException | None: |
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.
Simpler implementation:
def _get_single_subexc(
eg: BaseExceptionGroup[BaseException],
) -> BaseException | None:
if len(eg.exceptions) != 1:
return None
if isinstance(e := eg.exceptions[0], BaseExceptionGroup):
return _get_single_subexc(e)
return e
and isinstance(self.value, BaseExceptionGroup) | ||
and (subexc := _get_single_subexc(self.value)) is not None | ||
): | ||
return f"[in {type(self.value).__name__}] {subexc!r}" |
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.
Suggested change
return f"[in {type(self.value).__name__}] {subexc!r}" | |
return f"{subexc!r} [single exception in {type(self.value).__name__}]" |
as discussed in the issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #12943
As
ExceptionInfo
still doesn't have proper support for exception groups this continues upon the hacky solution from #10209, modifying the reprcrash as well.I find this solution ... incredibly hacky and ugly, and am not a fan that n==1 gets handled but not n==2. But conceptually it just gets really tricky to figure out what info to strip, and how to show that. If we're going with stripping structure & group messages we could extend this solution to something like
[in ExceptionGroup]: ValueError("foo"), TypeError("bar")
.EDIT: less hacky now that I moved the code to
ExceptionInfo.exconly