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
When an exception happens in a Python callable added via (Context|Function).add_callable, the error message is not specific, which makes it hard to debug.
Of course, one could wrap each callable in a try/except block, but that's tedious.
I understand that the error cannot really be raised directly to Python, as it has to go through the JS machinery, thereby losing most of the exception stack. But maybe one could at least write the traceback to stderr, eg. using PyErr_WriteUnraisable?
When an exception happens in a Python callable added via
(Context|Function).add_callable
, the error message is not specific, which makes it hard to debug.Of course, one could wrap each callable in a
try/except
block, but that's tedious.I understand that the error cannot really be raised directly to Python, as it has to go through the JS machinery, thereby losing most of the exception stack. But maybe one could at least write the traceback to
stderr
, eg. usingPyErr_WriteUnraisable
?This seems to be the way adopted by CFFI in absence of a specific handler.
The text was updated successfully, but these errors were encountered: