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
Ah… I am not trying to be obtuse, but where in my screen shot do you see the “debub icon”?
I’m looking at the ‘split’ screen, on the left my script, on the right the “ipdb>”. I don’t see the left ‘rendering’ the actual line of code in the right screen. It’s completely out of SYNC.
In my view, the line of code being executed on the right, s/b highligted on the left. As of over one (1) year ago, I still haven’ t see the “HIGHLIGHTER” function at all!! But I digress, why isn’t the left view rendered as executed in the right! Sorry, but that is a Fundemental aspect of this ‘render side by side’, and it’s not here.
My apologies if my previous transmission was in the genre of “Failure To Communicate”!
In the screenshot in the reply dated May 29 2025 3:42 Render Side by Side, !Python - #3 by Kevin_M_Wilson there is a little bug icon in the upper right corner just to the left of the text ‘Python 3 (ipykernel)’ adjacent the kernel status indicator in the corner. And to the left of the text ‘Notebook’. That bug icon is the debug icon. It is unactivated in your screenshot. The resource I linked to earlier that is in the JupyterLab documentation will show you how to activate it and use it to step through running your code interactively.
What you show in this screenshot in this last post has no relation to this. That is not a visual debugger and I don’t think is ‘connected’ in any way to leverage the abilities of JupyterLab. That is a legacy debugger meant for IPython, from when it was run in a console/terminal, not Jupyter.