News for hackers. Stuff that matters.

A comment on JupyterHub 1.0. Parent comment

Re:JupyterHub 1.0 by y4mi on Saturday May 04, 2019 @01:13PM (#19827769)
Debuggers are only really useful if you're trying to figure out why some object in your server doesn't do what you want it to.

I'd wager that almost no data scientists write object oriented code.. it's probably mostly done one calculation at a time. executed in the notebooks repl. So the value you get from ide debuggers is tiny, as you're already doing everything one step at a time.

[ Parent | on HN ]
Re:JupyterHub 1.0 by bonoboTP on Saturday May 04, 2019 @02:13PM (#19828160)
You still write functions and may want to inspect variable state in the middle of function execution.
[ Parent | on HN ]
Re:JupyterHub 1.0 by applecrazy on Saturday May 04, 2019 @09:58PM (#19830630)
Correct. RStudio has this feature, where variable values can be inspected in a sidebar. This would be a really useful feature for Jupyter, especially when running a Python kernel.
[ Parent | on HN ]
Re:JupyterHub 1.0 by timdumol on Sunday May 05, 2019 @01:00AM (#19831256)
There is a JupyterLab extension for that: https://github.com/lckr/jupyterlab-variableInspector
[ Parent | on HN ]
Re:JupyterHub 1.0 by bonoboTP on Monday May 06, 2019 @05:15PM (#19843955)
Does it work with variables that are local to a function? I don't mean inspecting global variables after having executed a cell, but local variables in the middle of a function execution.
[ Parent | on HN ]