You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever I debug a cell in an interactive window, it first stops at the interactiveshell.py even though I have not set a breakpoint there, so I have to hit F5 to get to the actual breakpoint.
I generally use justMyCode=False because I also want to step into libraries, but only where I set breakpoints.
This is related to microsoft/vscode-jupyter#9815, which is closed for comments.
Steps to reproduce:
Debug a cell with justMyCode=False.
Diagnostic data
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
XXX
Behaviour
XXX
Steps to reproduce:
XXX
Diagnostic data
launch.json configuration
XXX
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
XXX
Output for Python Debugger in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python Debugger)
XXX
Extension version: 2024.6.0
VS Code version: Code 1.90.2 (Universal) (5437499feb04f7a586f677b155b039bc2b3669eb, 2024-06-18T22:37:41.291Z)
OS version: Darwin arm64 22.6.0
Modes:
Remote OS version: Linux x64 6.2.0-36-generic
Connection to 'SSH: mikado' could not be established Canceled
Connection to 'ssh-remote+mikado' could not be established
Connection to 'SSH: mikado' could not be established Canceled
Remote OS version: Linux x64 6.2.0-36-generic
Python version (& distribution if applicable, e.g. Anaconda): 3.10.12
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): VirtualEnvironment
This is by design or really a side effect of just my code being off. The kernel is stepping through code and with just my code off this entry is hit. There's really no workaround without adding some sort of custom callstack filtering to debugpy for this exact situation. It would be like stepThroughAllCodeExceptTheKernel or something like that.
Thanks @rchiodo, i am closing the issue since this is not handle in the Python debugger extension. Feel free to create a feature-request in https://github.com/microsoft/debugpy.
Type: Bug
Behaviour
Whenever I debug a cell in an interactive window, it first stops at the
interactiveshell.py
even though I have not set a breakpoint there, so I have to hit F5 to get to the actual breakpoint.I generally use
justMyCode=False
because I also want to step into libraries, but only where I set breakpoints.This is related to microsoft/vscode-jupyter#9815, which is closed for comments.
Steps to reproduce:
Debug a cell with
justMyCode=False
.Diagnostic data
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Behaviour
XXX
Steps to reproduce:
Diagnostic data
launch.json
configurationOutput for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output for
Python Debugger
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython Debugger
)Extension version: 2024.6.0
VS Code version: Code 1.90.2 (Universal) (5437499feb04f7a586f677b155b039bc2b3669eb, 2024-06-18T22:37:41.291Z)
OS version: Darwin arm64 22.6.0
Modes:
Remote OS version: Linux x64 6.2.0-36-generic
Connection to 'SSH: mikado' could not be established Canceled
Connection to 'ssh-remote+mikado' could not be established
Connection to 'SSH: mikado' could not be established Canceled
Remote OS version: Linux x64 6.2.0-36-generic
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
Connection to 'SSH: mikado' could not be established Canceled
Connection to 'ssh-remote+mikado' could not be established
Connection to 'SSH: mikado' could not be established Canceled
A/B Experiments
The text was updated successfully, but these errors were encountered: