Issue
JupyterLab 3.0
comes with a full-fledged visual debugger
. But using it is only posssible if you're running a xeus-python
kernel. Other sources report that there are a few differences between xeus-python
and ipython
, but that the list of features that differ between the two is shrinking. So that's not really what I'm asking for here. Rather, what is it that distinguishes xeus-python
from ipython
that makes it suitable for a visual debugger as the one featured by JupyterLab 3.0
?
Solution
Rather, what is it that distinguishes xeus-python from ipython that makes it suitable for a visual debugger as the one featured by JupyterLab 3.0?
It's nothing particularly deep or interesting. Jupyter defines a debugger protocol that's a straightforward wrapper around the Debug Adapter Protocol. Kernels have to support this protocol to be usable with the JupyterLab debugger.
xeus-python supports this protocol. The IPython kernel does not. They're working on it; I think it's planned for IPython kernel 6.0 (not to be confused with IPython 6.0, which came out a while ago).
Answered By - user2357112
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.