justMyCode: false yields error "This configuration can only be used as defined by `purpose`."

[CristianCapsuna]

Environment data

• VS Code version: 1.60
• Extension version (available under the Extensions sidebar): Python v2021.9.1191016588, Jupyter v2021.8.2041215044, Jupyter Keymap v1.0.0, Remote WSL v0.58.2
• OS and version: Windows 10, 10.0.19042
• Python version (& distribution if applicable, e.g. Anaconda): 3.9.7
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
• Relevant/affected Python packages and their versions: scikit-learn 0.24.2
• Value of the python.languageServer setting: where can I find this?

Expected behaviour

The debugger starts and is able to step out of open file and follow the code to whatever module it goes to.

Actual behaviour

Debugging does not start and I get the message/error: "This configuration can only be used as defined by purpose."

Steps to reproduce:

1. Create a virtual environment
2. Install pandas, scikit-learn, sqlalchemy, nltk
3. Copy file from here
4. Download data file and place in the same place as file from point above.
5. Place breakpoint on line cv.fit(X_train, y_train).
6. Add launch.json file as detailed here. To find the configuration search for "For example, the configuration below in the launch.json file disables the justMyCode setting for debugging tests:"
7. Launch debugger on the file.

[karthiknadig]

The issue is not justMyCode. In your debug configuration "request": "test", is no longer supported. Change that to "request": "launch", and add "purpose": ["debug-test"],.

[CristianCapsuna]

Hi Karthik. Thank you for your comment. If you find the configuration mentioned in point 6, those amendments are included in there, which is my starting point.

The starting point:

My actual launch.json file:

Debugging does not start and this message is displayed:

[karthiknadig]

@CristianCapsuna debug-test configurations can only be used with Test explorer or test debug commands from the command pallet. You cannot use that to do file debugging. This is because we change the configuration a bit depending on which test or test case you launch it on.

For example, we remove "program": "${file}" from the configration, because you can't launch pytest test directly as a file you have to launch it via the pytest module. So the configuration gets modified depending on the scenario.

To debug a file add a configuration specifically for that. For your scenario, add two configurations. Use the current file configuration for the debugging a file:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "justMyCode": false
        },
        {
            "name": "Test Config",
            "type": "python",
            "request": "launch",
            "purpose": ["debug-test"],
            "justMyCode": false
        }
    ]
}

[CristianCapsuna]

Hi Karthik. Thank you for taking the time and looking at this problem. I have tried copy and pasting the configs you have provided into my launch.json. I have also tried leaving just the second one by itself. Both yielded the same message that I showed in my previous comment. Has it worked for you? I might be doing something stupid so will read the documentation on debugging in VS Code to see if I can find out what is happening.

[heungson]

I also have the same issue.

[mhaley-tignis]

I had an issue that seems to stem from the https://marketplace.visualstudio.com/items?itemName=LittleFoxTeam.vscode-python-test-adapter extension. It still supports "request": "test" and seems to muck around with the default explorer such that the default explorer will not pick up the configurations described in previous comments. Disabling the Python Test Explorer for Visual Studio Code by Little Fox Team solved my problems.