JupyterLab Visual Debugger and xeus‑python Kernel: Installation, Features, and Front‑End Architecture
The article introduces JupyterLab’s new visual debugger, explains why debugging is needed in Jupyter, provides installation commands for the front‑end extension and xeus‑python kernel, describes the debugger’s UI components and capabilities, and compares it with a VS Code visual debugging tool.
JupyterLab now offers a visual debugger, enabling breakpoint setting, variable inspection, and execution control directly within notebooks, addressing the long‑standing lack of visual debugging in Jupyter.
To use it, install the front‑end extension with jupyter labextension install @jupyterlab/debugger and the back‑end kernel conda install xeus-python -c conda-forge , which implements the Jupyter Debug Protocol.
xeus‑python, the first kernel to support Jupyter debugging, provides a pluggable concurrency model and a lightweight codebase, making it suitable for building language kernels such as Python.
The debugger UI adds a side‑panel file explorer, source preview, call‑stack navigation, inline breakpoint toggles, and visual markers indicating the current execution point, plus variable browsers and tree/graph visualizations.
Demo GIFs show debugging of deleted cells, console debugging, multi‑notebook debugging, and variable inspection, while future plans include richer variable rendering and conditional breakpoints.
A related VS Code visual debugging tool is also highlighted, featuring real‑time data‑structure visualizations such as linked lists, trees, tables, and Plotly charts.
Additional resources and a QR code are provided for a free Python public course and related learning materials.
Python Programming Learning Circle
A global community of Chinese Python developers offering technical articles, columns, original video tutorials, and problem sets. Topics include web full‑stack development, web scraping, data analysis, natural language processing, image processing, machine learning, automated testing, DevOps automation, and big data.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.