Closed eudoxos closed 3 years ago
Can you elaborate how this is different from the default mechanism?
https://pyro5.readthedocs.io/en/latest/errors.html#remote-exceptions
I was trying to inject the remote traceback at the end of the local one so that usual exception reporting would report the remote part as well. But it has a number of drawbacks (such as that modules have to be installed on the local machine as well), the existing mechanism with extended reporting is fine. Sorry for noise, closing.
no problem, glad you can continue with the existing mechanism.
I find this quite helpful when debugging - the traceback shows both the local and remote part. It introduces a dependency on
tblib
(for serializing the traceback object) which might or might not be acceptable.