Evaluate in second notebook

[masip85]

Hello

I've been following this:
https://miro.medium.com/max/700/0*ZejsDIpKOEPDgoTs.gif

But I've realised that the secondary notebook is not useful for evaluating or writing code when the debug process is stopped at a breakpoint. I mean, I thought writing in the secondary notebook would let me play with variables of the debugging process scope.

If in the -gif example- secondary notebook, you write in the new cell[2] and execute it, it has to wait to debug finishes.

So, is there anyway to "play" with debug internal scope?

[JohanMabille]

Hi,

This is not supported yet. Further developments are required to plug the Evaluate request into Jupyterlab UI.

[masip85]

Oh, it looks like long and difficult. is it in future release scope?

[JohanMabille]

Not that long and difficult, the backend already supports it, it's more a matter of deciding how we want to integrate that in the UI (dedicated panel? Juyter Console?). And yes, we plan to implement it at some point.

[masip85]

Interesting decision. If you ask me my opinion - I know you don't but I'd like to give my point of view-, I would say dedicated panel is the normal way,but, debugging in data science sometimes require tables, so jupyter notebook console is a great starting point. I mean,from this:
https://miro.medium.com/max/700/0*ZejsDIpKOEPDgoTs.gif
just give the user the ability to add in the bottom cell what is wanted to be evaluated -just like notebook console does-

[JohanMabille]

Any constructive opinion is welcome ;) I agree that a Jupyter Console would give more possibilities regarding rich display.