Sorry, something went wrong.
|
I haven't created an issue for this because I figured it's just a documentation fix but I can create one if necessary. We do create issues for documentation changes as well (unless trivial, as in typo). |
Sorry, something went wrong.
|
Subinterpreters got hit by property-based tests, gonna retrigger the run |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good, a few more minor suggestions.
Sorry, something went wrong.
|
Thanks @Jackenmen for the PR, and @iritkatriel for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
Sorry, something went wrong.
|
GH-105066 is a backport of this pull request to the 3.12 branch. |
Sorry, something went wrong.
|
GH-105067 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
It seems that exceptions have been missed when the exception groups were added in 3.11.
There are also two new parameters to TracebackException(...) - max_group_depth and max_group_width. I have only added the documentation for the parameters, not the attributes as modifying the latter wouldn't propagate the value to chained/grouped TracebackExceptions but I can add them if you wish.
I reused the issue number of the original issue that added these parameters/attributes.
I'm sorry for accidentally pinging so many people on #105043, GitHub doesn't warn you about the possibility of pinging people when changing the base :(
📚 Documentation preview 📚: https://cpython-previews--105044.org.readthedocs.build/