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 a Python error is thrown, the error message includes a full trackback of what went wrong.
This is probably great for software development/debugging. However, as a Notebook user working on a Data Science project, the most likely causes of errors are: typos in functions/variables, incorrectly called functions/parameters, or other mistakes on my end.
The most useful bits of information that help me identify the root cause of the error are:
The ErrorType (what went wrong)
The Traceback calls for the notebook itself (where did it go wrong in my code)
Problem
The most useful debug information is printed at the end of the Python error message. This works for traditional Python files, as the error output is printed to the terminal. Errors in Notebooks are however viewed from start (top) to end (bottom). This means that users have to scroll to the end of the error message, to view the most important debug information.
This is a pain, especially for errors with long tracebacks.
Improvement suggestion
[ either as an option / or by default ]
Show concisely formatted Error messages, when an error occurs within a Notebook file (geared towards Data Science users). Include the following bits of information:
The Error Type
Only tracebacks of code within the Jupyter Notebook (not from dependencies like pandas/numpy).
Description
When a Python error is thrown, the error message includes a full trackback of what went wrong.
This is probably great for software development/debugging. However, as a Notebook user working on a Data Science project, the most likely causes of errors are: typos in functions/variables, incorrectly called functions/parameters, or other mistakes on my end.
The most useful bits of information that help me identify the root cause of the error are:
Problem
The most useful debug information is printed at the end of the Python error message. This works for traditional Python files, as the error output is printed to the terminal. Errors in Notebooks are however viewed from start (top) to end (bottom). This means that users have to scroll to the end of the error message, to view the most important debug information.
This is a pain, especially for errors with long tracebacks.
Improvement suggestion
[ either as an option / or by default ]
Show concisely formatted Error messages, when an error occurs within a Notebook file (geared towards Data Science users). Include the following bits of information:
Example error code:
Concisely formatted error message:
Current error message:
The text was updated successfully, but these errors were encountered: