Can Transformer be less naive when using VisitError?

The new VisitError is great, but it come with a problem. If I am raising an error inside a transformer function, VisitError catches it and formats it, so there’s no way to retrieve the original error.

Of course the problem in the first place is that there is a catch-all statement that does not leave any room for custom error handling. A simple handle_errors flag that could be passed to Transformer.transform and disable Transformer raising VisitError and letting the error go would work, but there are many ways to achieve this.

[erezsh]

Pushed a fix to master.

You can now do something like:

try:
    T().transform(tree)
except VisitError as e:
    raise e.orig_exc

Is that good enough, or do you still want an option to disable VisitError wrapping?

[chaosite]

The exception object itself is not the only thing that is lost by wrapping the exception, you also lose the exception context, so pdb post-mortem is much less helpful.