Disabling debugpy.debugJustMyCode in settings.json doesn't apply to the debug-test purpose in launch.json

[blakeNaccarato]

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 in launch.json.
  • We specify debug-test in our purpose.
  • We do explicitly disable the global setting debugpy.debugJustMyCode in settings.json.
  • We cannot stop at breakpoints in standard library code here.
• ✅ 2-debugpy-adapter: Here we explicitly disable justMyCode in launch.json and specify debug-test in our purpose. We successfully stop at breakpoints in standard library code here.
• ✅ 3-vscode-python-debug-adapter: Here we use the soon-to-be-deprecated python debug adapter, explicitly disable justMyCode in launch.json, and specify debug-test in our purpose. 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

[rzhao271]

Python Debugger: v2024.9.2024072301 (pre-release)
Python: v2024.11.2024072302 (pre-release)

Case 1 is still failing for me above. When I set a breakpoint for json.dumps in .conda\Lib\json\__init__.py and run the "Python Debugger: Current File" launch config on test_sample.py, the debugger does not stop at the breakpoint.

[blakeNaccarato]

I can confirm that Case 1 is still failing for me as well, with the same setup as my original post, but with v2024.9.12041011 (pre-release) of the Python Debugger extension. I've added a VSCode workspace file to my minimal repro repo that demonstrates the cases side-by-side, with cases two and three working, but case one still not working.

I'm using vanilla virtual environments via Python's venv module, though I see conda's also showing the issue. Also there was a test discovery regression in pytest==8.3.1 affecting conda that's already fixed but not in a new release, so be aware of that when working on this issue.

[andreamah]

@brettcannon did you close this because the issue has been resolved? Otherwise, we would want to keep it open.

[paulacamargo25]

Can someone test again? i am adding verification steps.

Verification Steps:

1. Create a simple unittest in python that uses an external library.
2. Add a breakpoint in the function call.
3. Update debugpy.debugJustMyCode to true
4. Try to step into the external library.

[rzhao271]

Re-verified and LGTM.

It looks like running the launch config on sample.py works, and that running the launch config on test_sample.py works after explicitly adding a call to the test_answer() test function. I'm unsure whether the launch config could directly run a test for you.

[brettcannon]

@brettcannon did you close this because the issue has been resolved? Otherwise, we would want to keep it open.

It closed because GitHub thought my syncing of the main branch on my fork meant it should re-apply all of the "Closes" comments.