You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like no RAISE event is emitted for a bare raise in an except: clause or at the end of a finally: clause that implicitly reraises an exception. I don't know whether this a problem with the implementation or it should simply be documented that this is to be expected.
I mentioned this in #103082 but was encouraged to create a separate bug for it.
We should emit an event for these cases, as the "exception raised" events, and "exception handled" events should balance.
There are quite a lot of exception events during unwinding however, so this could be quite noisy.
For example:
deffunc():
try:
try:
1/0except:
raiseexcept:
pass
generates 3 raise/handled pairs. The obvious 2, plus another for cleanup, which is highly implementation dependent.
If we generate normal RAISE events it will break sys.settrace, so we need to emit a different event. RERAISE is the obvious name.
Uh oh!
There was an error while loading. Please reload this page.
It looks like no RAISE event is emitted for a bare raise in an except: clause or at the end of a finally: clause that implicitly reraises an exception. I don't know whether this a problem with the implementation or it should simply be documented that this is to be expected.
I mentioned this in #103082 but was encouraged to create a separate bug for it.
Linked PRs
RERAISE
event tosys.monitoring
. #107291RERAISE
event tosys.monitoring
. (GH-107291) #107346The text was updated successfully, but these errors were encountered: