bpo-45292: add ExceptionGroup formatting in tracebacks #31
Conversation
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
… not yet update traceback formatting)
iritkatriel
force-pushed
the
bpo-45292-traceback
branch
from
09b9c81 to
717f4ab
Compare
iritkatriel
force-pushed
the
bpo-45292-ExceptionGroup
branch
4 times, most recently
from
fee53c9 to
dbd72d1
Compare
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.
This is the basic thing, once this is reviewed we can look at showing less redundant information (for internal EGs).
I think the "with X sub-exceptions" line is not adding clarity and should be removed. Let me know if any objections.