Description
I'm using "Python Debugger" extension v2024.6.0
. It looks like microsoft/vscode-python#22903 closed related issues #174 and #112, but this is not exactly the same issue. Basically, disabling debugpy.debugJustMyCode
in settings.json
doesn't apply to the debug-test
purpose
in launch.json
. See https://github.com/blakeNaccarato/vscode-python-debugger-335 for a minimal repro of three behaviors. The subfolders represent three different debug configurations:
- ❌
1-debugpy-adapter-settings-justmycode
- Here we omit
justMyCode
inlaunch.json
. - We specify
debug-test
in ourpurpose
. - We do explicitly disable the global setting
debugpy.debugJustMyCode
insettings.json
. - We cannot stop at breakpoints in standard library code here.
- Here we omit
- ✅
2-debugpy-adapter
: Here we explicitly disablejustMyCode
inlaunch.json
and specifydebug-test
in ourpurpose
. We successfully stop at breakpoints in standard library code here. - ✅
3-vscode-python-debug-adapter
: Here we use the soon-to-be-deprecatedpython
debug adapter, explicitly disablejustMyCode
inlaunch.json
, and specifydebug-test
in ourpurpose
. We successfully stop at breakpoints in standard library code here.
Could debugpy.debugJustMyCode
global toggle in settings.json
be extended to cover test debugging as well?
It's nice to have a global toggle for this, so that a launch.json
config checked into the repo doesn't have a merge-conflict-prone justMyCode
toggle embedded in it.
Here's the output of my VSCode Help > About
:
Version: 1.88.1 (user setup)
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:41:02.734Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631