In
and
|
return super(EventSift, self).__call__(event) |
there is a
return statement in a
finally block, which would swallow any in-flight exception.
This means that if any exception (including BaseException such as KeyboardInterrupt) is raised from the try body, it will not propagate on as expected.
See also https://docs.python.org/3/tutorial/errors.html#defining-clean-up-actions.
In
PyDev.Debugger/pydevd_attach_to_process/winappdbg/event.py
Line 1478 in 7d6e6e6
and
PyDev.Debugger/pydevd_attach_to_process/winappdbg/event.py
Line 1635 in 7d6e6e6
there is a
returnstatement in afinallyblock, which would swallow any in-flight exception.This means that if any exception (including
BaseExceptionsuch asKeyboardInterrupt) is raised from thetrybody, it will not propagate on as expected.See also https://docs.python.org/3/tutorial/errors.html#defining-clean-up-actions.