-
Notifications
You must be signed in to change notification settings - Fork 295
How debuggers work
Rich Chiodo edited this page Aug 4, 2022
·
7 revisions
There are many forms of debugging in the Jupyter extension. This page seeks to describe how they all work from the extension developer's point of view.
The known forms of debugging are:
- Launching a python script in the debugger (not really this extension, but a good way to describe how debugging works in VS code)
- Debugging a cell in the interactive window
- Debugging a cell in a notebook
- Running by line in a cell of a notebook
For documentation on how to use these forms of debugging check here:
- Python script debugging
- Interactive window debugging
- Debugging a cell in a notebook
- Running by line in a notebook
Troubleshooting:
- 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