-
Notifications
You must be signed in to change notification settings - Fork 326
How interactive debugging works (old way)
The Interactive Window is used for running cells in a python script. One of the capabilities of running these cells is to debug them.
This page will describe how this debugging is implemented under the covers.
<!--
Generated at https://sequencediagram.org/ with the following text:
title Interactive Window Debugging
participant VS Code#lightgreen participant Jupyter#lightblue participant Kernel#lightyellow VS Code->Jupyter:Debug cell clicked Jupyter->VS Code:Debug attach Jupyter->Kernel:Replace kernel's run cell handler Jupyter->Kernel:Remap source files Jupyter->Kernel:Enable thread tracing Jupyter->Jupyter:Add breakpoint to source Jupyter->Kernel:Execute cell with new source Kernel->VS Code:Stop Event -->
This sequence diagram is explained below:
- Contribution
- Source Code Organization
- Coding Standards
- Profiling
- Coding Guidelines
- Component Governance
- Writing tests
- Kernels
- Intellisense
- Debugging
- IPyWidgets
- Extensibility
- Module Dependencies
- Errors thrown
- Jupyter API
- Variable fetching
- Import / Export
- React Webviews: Variable Viewer, Data Viewer, and Plot Viewer
- FAQ
- Kernel Crashes
- Jupyter issues in the Python Interactive Window or Notebook Editor
- Finding the code that is causing high CPU load in production
- How to install extensions from VSIX when using Remote VS Code
- How to connect to a jupyter server for running code in vscode.dev
- Jupyter Kernels and the Jupyter Extension