No error traceback of code input about widget-code-input HOT 3 CLOSED

Here is an example notebook where I add some wrapper code to display better information, both for SyntaxErrors when parsing the code, and then for any other exception (including NameError) when executing it:
code-widget-syntax-error-example-checkpoint.ipynb.zip

If you like the approach and the output, probably we need to think at how to put this code directly in the code widget (e.g., having the two wrapper codes directly wrapping the calls to get_function_object and wrapping the actual execution) to avoid that the user has to remember to wrap them every time?

@dou-du @agoscinski happy to hear feedback on the suggested approach, and possibly to the integration in the code widget

from widget-code-input.

I proposed a solution. However I worked on master, while I think I should have done it in develop? This includes the two commits I directly pushed to add black and other pre-commits... @dou-du let me know if you know how to fix it, or we should discuss

from widget-code-input.

I would say there is no need to catch the error in case of an SyntaxError when getting the function object in wid.widget_function_object(), since the error is displayed correctly in this case.

I was hoping there is an approach that forwards to the python error machinery such that we do not have this hacky way of imitating the python error message. But it seems to be a general problem of python for executed strings.
https://stackoverflow.com/questions/35564208/python-traceback-of-a-string-in-exec

So I am fine with this solution. I would just keep the same error type name add the proper coloring to the error message.
https://stackoverflow.com/a/287944

from widget-code-input.