Live data from Hacker News

A Visual Debugger for Jupyter

blog.jupyter.org

51–60 of 74 posts

Re: A Visual Debugger for Jupyter

#51
post #33

When will jupyter have "highlight and execute" functionality? The cell concept is fine, but I'm constantly copy pasting snippets of code into new cells to get that "incremental" coding approach...

It has already been in JupyterLab for more than a year. You just need to attach a kernel console to your text file.

Re: A Visual Debugger for Jupyter

#52
post #37

Been wondering about this for a while... How does one "graduate" a notebook to an actual program on a server? Is there an actual standard procedure for that? I'm pretty sure that if your notebook is big enough to debug what's in it you'd be doing everyone a disservice keeping it contained like that.

Along those lines, what's wrong with using free and open source editors with great debug support such as VSCode? I don't understand the appeal of using Jupyter notebooks unless you're plotting or documenting.

Re: A Visual Debugger for Jupyter

#53

Who cares? Once you're editing text in a browser you've failed.

are you blind? this is a comment on a post about jupyterlab - a browser based IDE.

You've been posting a shocking number of nasty swipes at people. If you keep doing this we are going to have to ban you again. Would you please just follow the site guidelines instead?

https://news.ycombinator.com/newsguidelines.html

Re: A Visual Debugger for Jupyter

#54

I'm a programmer, mostly not a data scientist nowadays, mostly working with Python. I have tried Jupyter Lab/Notebook on and off over the last 10 years, and I believe I have now firmly settled on my conclusion: Everyone should aim to minimize the amount of work they do in Jupyter Lab / Notebook. It shocks me a bit to find myself saying that, as it is such a beautiful piece of work. Furthermore the people who wrote it…

Are there projects to integrate notebooks with version control?

This is the most promising one I'm aware of. I tried it in the course of trying not to accept the conclusion I outlined above.

https://github.com/mwouts/jupytext

Re: A Visual Debugger for Jupyter

#55
This animated GIF shows the new debugger in action, allowing point-and-click step-by-step execution at breakpoints and easy inspection of variables, call stack, and source code: https://miro.medium.com/max/1400/1*NP0bYBdrhwgpJpKDhPLWrQ.gi...

It looks to be a very welcome improvement for those of us who routinely use Jupyter notebooks for "REVL" (read-eval-visualize-loop) experimentation.

Has anyone here had a chance to test how well this works with objects from Python's scientific stack such as numpy arrays, pandas dataframes, matplotlib objects, PyTorch and TensorFlow CPU/GPU tensors, and so on?

Re: A Visual Debugger for Jupyter

#56

I'm a programmer, mostly not a data scientist nowadays, mostly working with Python. I have tried Jupyter Lab/Notebook on and off over the last 10 years, and I believe I have now firmly settled on my conclusion: Everyone should aim to minimize the amount of work they do in Jupyter Lab / Notebook. It shocks me a bit to find myself saying that, as it is such a beautiful piece of work. Furthermore the people who wrote it…

As a data scientist who spends at least half my time in Jupyter, I wholeheartedly agree with this.

Re: A Visual Debugger for Jupyter

#57
post #37

Been wondering about this for a while... How does one "graduate" a notebook to an actual program on a server? Is there an actual standard procedure for that? I'm pretty sure that if your notebook is big enough to debug what's in it you'd be doing everyone a disservice keeping it contained like that.

I gradually graduate a notebook by extracting what I can into libraries, and importing those utilities into the notebook. Eventually the logic in the notebook becomes trivial enough to easily convert into a production program.

Re: A Visual Debugger for Jupyter

#58
post #37

Been wondering about this for a while... How does one "graduate" a notebook to an actual program on a server? Is there an actual standard procedure for that? I'm pretty sure that if your notebook is big enough to debug what's in it you'd be doing everyone a disservice keeping it contained like that.

Someone at IBM turned a notebook into an RPC callable micro-service. I've adapted that idea too, and put an http (gcloud/away compatible) wrapper around all my functions. It was here but that is apparently gone. http://blog.ibmjstart.net/2016/01/28/jupyter-notebooks-as-re...

Re: A Visual Debugger for Jupyter

#59
post #53

Earlier quoted context omitted.

are you blind? this is a comment on a post about jupyterlab - a browser based IDE.

You've been posting a shocking number of nasty swipes at people. If you keep doing this we are going to have to ban you again. Would you please just follow the site guidelines instead? https://news.ycombinator.com/newsguidelines.html

>You've been posting a shocking number of nasty swipes at people.

i don't take swipes at people who don't post vile things to begin with. i will never understand the whole "you have to tolerate the intolerant" ethos. you can peruse my comments (as you have) - i never incite but censure is a public service.

Re: A Visual Debugger for Jupyter

#60
post #37

Been wondering about this for a while... How does one "graduate" a notebook to an actual program on a server? Is there an actual standard procedure for that? I'm pretty sure that if your notebook is big enough to debug what's in it you'd be doing everyone a disservice keeping it contained like that.

For a visual output, voila can give you a dashboard look: https://github.com/voila-dashboards/voila/ see e.g. https://github.com/maartenbreddels/voila-demo for a mobile-ready responsive rendering of a notebook.
Post reply on HN