Unexpected location of naked exception wrapped in except* block #128799
Labels
interpreter-core
(Objects, Python, Grammar, and Parser dirs)
type-bug
An unexpected behavior, bug, or error
Bug report
Bug description:
When an
ExceptionGroup
is implicitly constructed by catching a naked exception in anexcept*
block, the traceback of theExceptionGroup
seems to point to the stackframe above where it is logically created:→
I'm not sure if this should be called a bug, as it's not specifically documented how the wrapping ExceptionGroup traceback is constructed. But it is surprising, and did cause a bug in hypothesis where the Exception traceback is used to detect whether an exception originates in hypothesis itself or in user code 12. The issue being that for wrapped naked exceptions we have to inspect the inner exception since the outer exception appears to be raised by the calling function.
As an alternative to the current behaviour, would it be possible to create the wrapper ExceptionGroup with a traceback pointing to where it is logically triggered - i.e., the
except*
block - rather than initially empty? IMO, that would be less suprising and would allow us to use the traceback without special-casing ExceptionGroup.([edit] Or, if the desire is to avoid branching the traceback between the wrapper and the inner exception, use the outermost frame of the naked exception as the initial ExceptionGroup traceback. This would still avoid the appearance of happening in the caller.)
CPython versions tested on:
3.11, 3.12, 3.13
Operating systems tested on:
Linux
Footnotes
https://github.com/HypothesisWorks/hypothesis/issues/4183 ↩
https://github.com/HypothesisWorks/hypothesis/pull/4239 ↩
The text was updated successfully, but these errors were encountered: