As can be seen, the scroll of the execution of my script, and where that is in the actual script is not in alginment!
Suggestion:
Two (2) scroll tools on the script, and on the debug of the script are needed!
BADLY, otherwise, why have one that does allow for a more optimum debug ‘experience’?! Oh, can one of ya’ll holla back, Please?
There is a visual debugger introduced in the JupyterLab documentation here. That is meant for current JupyterLab.
It seems what you show comes from back when Python is was run in a text-based console or terminal, not integrated in a browser-based UI.
My version (Version 4.3.4) as of 05/29/25, I hadn’t been informed of another debugger for Jupyter NB and the Udemy Zero to Hero Python tutorial? I’m not a command line guy with Juypter NB, so you mentioned ‘visual’ debugger, I’ve used Eclipse, Java, MS .NET for C/C++/C#/VB, and so on. I’m not familiar w/Juypter NB’ visual debugger? In past experiences, I just down load the .NET’s for ‘C’ language IDE w/debugger. As for “text-based console/terminal…”
Unfortnately it’s now opening in MS Edge, not sure why that is, as I use Chrome for Python!
Oh! Please do tell, how I bypass the “new users only one embedded picture” SNAP!
It’s not ‘another’ debugger. It is the one for JupyterLab. I see the bug icon in the upper corner of your screenshot.
You have to activate it and use it as illustrated in the material I referenced.
I cannot comment on some tutorial I haven’t seen, but the fact it has Python in it makes me wonder if it is targeted at Python in general and intentionally not fully taking advantage of the abilties of JupyterLab that you won’t have access to in other places.
1 Like