Currently, if there is an exception inside a function called with call_python(), it ends up being consumed by dukpy and gets translated into a dukpy.JSRuntimeError.
However, dukpy itself seems to have all the necessary information to just rethrow this exception to the caller of evaljs(), which would be more useful for error handling. If preserving existing behaviour is necessary, maybe it could be an optional argument to evaljs() that is set to False by default.
This is more of a feature request.
Currently, if there is an exception inside a function called with
call_python(), it ends up being consumed by dukpy and gets translated into adukpy.JSRuntimeError.However, dukpy itself seems to have all the necessary information to just rethrow this exception to the caller of
evaljs(), which would be more useful for error handling. If preserving existing behaviour is necessary, maybe it could be an optional argument toevaljs()that is set toFalseby default.Is this something that could be added?