microsoft / microsoft/vscode-python-debugger

Debug configuration does not override workspace python interpreter

Offen
#463 4 Kommentare 1 Reaktion 1 zugewiesene Person Auf GitHub ansehen

@eleanorjboyd arbeitet bereits daran.

Seit 30.9.2024.

triage-needed
Vorherrschende Sprache
TypeScript
Sterne
180
Forks
126
Ø Merge
2 T. 3 Std.
Gemergte PRs (30 T.)
3

Beschreibung

Fairly straightforward issue. When performing "Start Debugging" or "Run Without Debugging", the debugger will use the current workspace interpreter instead of the interpreter specified in the launch.json configuration with the "python" key.

Steps to reproduce:

  1. Have a multi-folder/root workspace. E.g.:
    • .vscode
      • launch.json
    • ProjectA
      • projecta-abcd-py3.x
      • etc
    • ProjectB
      • projectb-abcd-py3.x
      • etc
  2. Specify the interpreter you want each debug configuration to use in your launch.json file. E.g.:
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "ProjectA",
            "type": "debugpy",
            "python": "${workspaceFolder}/projectA/projecta-abcd-py3.x/bin/python",
            "request": "launch",
            "program": "${workspaceFolder}/projectA/cli.py",
            "console": "integratedTerminal",
            "args": []
        },
        {
            "name": "ProjectB",
            "type": "debugpy",
            "python": "${workspaceFolder}/ProjectB/projectb-abcd-py3.x/bin/python",
            "request": "launch",
            "program": "${workspaceFolder}/ProjectB/cli.py",
            "console": "integratedTerminal",
            "args": []
        },
    ]
}
  1. Set your workspace interpreter to the interpreter for any project. Let's say we set it to A, ./projectA/projecta-abcd-py3.x/bin/python.
  2. Select the run & debug configuration for a different project. Let's say we select B.
  3. Start Debugging or Run Without Debugging.

Expected result (terminal output):

source /home/REDACTED/ProjectB/projectb-abcd-py3.x/bin/activate
user@host:~/REDACTED$ source /home/REDACTED/ProjectB/projectb-abcd-py3.x/bin/activate
(projectb-py3.x) user@host:~/REDACTED$  /usr/bin/env /home/REDACTED/ProjectB/projectb-abcd-py3.x/bin/python /home/REDACTED/.vscode-server/extensions/ms-python.debugpy-2024.10.0-linux-x64/bundled/libs/debugpy/adapter/../../debugpy/launcher 41261 -- /home/REDACTED/ProjectB/cli.py

Actual result (terminal output):

source /home/REDACTED/ProjectA/projecta-abcd-py3.x/bin/activate
user@host:~/REDACTED$ source /home/REDACTED/ProjectA/projecta-abcd-py3.x/bin/activate
(projecta-py3.x) user@host:~/REDACTED$  /usr/bin/env /home/REDACTED/ProjectA/projecta-abcd-py3.x/bin/python /home/REDACTED/.vscode-server/extensions/ms-python.debugpy-2024.10.0-linux-x64/bundled/libs/debugpy/adapter/../../debugpy/launcher 41261 -- /home/REDACTED/ProjectB/cli.py

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.