Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

"Show automatic Python configurations" button does not update when the active editor changes

未關閉
#1,122 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
72/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
typescript, vscode

研究方向

Read package.json around lines 692–698 and src/extension/extensionInit.ts around lines 245–249 to trace how dynamicPythonConfigAvailable controls the welcome-view button. Compare the two proposed fixes, then check the existing tests for context keys or active-editor changes. Done means the button reflects the active editor’s language and does not offer to run a non-Python file with debugpy.

由索引模型根據 Issue 內容生成。

描述

triage-needed

The extension contributes a "Show automatic Python configurations" button to the welcome view of Run and Debug. The dynamicPythonConfigAvailable context key controls this button:

https://github.com/microsoft/vscode-python-debugger/blob/3351fdf239de2111c7033cfe0ef386b058de4c7f/package.json#L692-L698

The extension sets this context key one time, during activation:

https://github.com/microsoft/vscode-python-debugger/blob/3351fdf239de2111c7033cfe0ef386b058de4c7f/src/extension/extensionInit.ts#L245-L249

No code updates the key after activation. As a result, the button shows the language of the editor that was active when the extension activated, not the language of the current editor. This causes two problems:

  1. The button stays visible for non-Python files. The extension usually activates through onLanguage:python, so the key becomes true. If you then open a JavaScript or TypeScript file, the button stays in the view.
  2. The button can stay hidden for Python files. If the extension activates through a debug activation event while a non-Python file is active, the key becomes false. The button does not show when you open a Python file later.

Many projects use Python together with other languages, for example a Python backend with a TypeScript frontend. In these projects, the button often shows for files that debugpy cannot debug.

The first problem can also start the wrong program. The button runs workbench.action.debug.selectandstart for debugpy. The first dynamic configuration is "Python Debugger: Python File", with "program": "${file}". If a non-Python file is active, debugpy tries to run that file as Python.

Steps to reproduce
  1. Open a folder that has a Python file and a non-Python file (for example, app.py and index.js). Do not add a launch.json.
  2. Open app.py.
  3. Open the Run and Debug view. The "Show automatic Python configurations" button shows. This is correct.
  4. Open index.js.
  5. Look at the Run and Debug view again.

Expected: The button does not show, because the active file is not Python.

Actual: The button continues to show. If you click it and select "Python Debugger: Python File", debugpy tries to run index.js as a Python program.

Possible fixes

I am very happy to contribute a PR for this! Two options seem good from my perspective:

  • Update the key when the active editor changes. Add a window.onDidChangeActiveTextEditor listener that sets dynamicPythonConfigAvailable again. This would be the smallest change.
  • Use the context keys of the workbench. The core debug welcome view already tracks the language of the active editor with debugStartLanguage and debuggerInterestedInActiveEditor. The when clause can change to debugStartLanguage == python && debuggerInterestedInActiveEditor && !virtualWorkspace, and the extension can stop setting its own key.
主要語言
TypeScript
星號
184
分支
129
平均合併
4 天 17 小時
30 天內合併 PR
5

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

microsoft/vscode-python-debugger 的其他 Issue

查看 microsoft/vscode-python-debugger 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。