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
The most important information to solve an error in your code is arguably the error message (the exception that was raised). This bit of information is printed at the bottom of the stack trace.
When a developer knows the Error message - the most common error's like typo's in variables/functions - or incorrectly called functions/ parameters can be fixed right away.
Current situation
The Error message is printed at the bottom of the stack trace. This works for traditional python development, as the stack trace is printed to the console/output window. Stack traces in a notebook are however viewed from top to bottom.
This is problematic in case of long stack traces (common for errors that originate from packages like pandas/ numpy). To resolve the error, the user will have to scroll down and up multiple pages (to inspect the error messages -- and subsequently fix it in their code).
Suggestion
Include a copy of the Error message at the top of the stack trace.
This way the code containing the error -- and Error message are always visible in the same view.
Mockup
Example error code
import pandas as pd
chipo = pd.read_csv("https://raw.githubusercontent.com/justmarkham/DAT8/master/data/chipotle.tsv", sep="\t")
chipo.groupby('item_name').sum()['item_price']
The text was updated successfully, but these errors were encountered:
Hi, Thanks for this very useful tip. I am new to JupyterLab. Can you kindly recommend how I can run this script for all my notebooks without putting it in every file? Alex
The most important information to solve an error in your code is arguably the error message (the exception that was raised). This bit of information is printed at the bottom of the stack trace.
When a developer knows the Error message - the most common error's like typo's in variables/functions - or incorrectly called functions/ parameters can be fixed right away.
Current situation
The Error message is printed at the bottom of the stack trace. This works for traditional python development, as the stack trace is printed to the console/output window. Stack traces in a notebook are however viewed from top to bottom.
This is problematic in case of long stack traces (common for errors that originate from packages like pandas/ numpy). To resolve the error, the user will have to scroll down and up multiple pages (to inspect the error messages -- and subsequently fix it in their code).
Suggestion
Include a copy of the Error message at the top of the stack trace.
This way the code containing the error -- and Error message are always visible in the same view.
Mockup
Example error code
The text was updated successfully, but these errors were encountered: