Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#1,122 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
72/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
typescript, vscode
Domínio
developer-experience

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
TypeScript
Estrelas
182
Forks
125
Merge médio
4d 17h
PRs com merge (30d)
5

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de microsoft/vscode-python-debugger

Todas as issues de microsoft/vscode-python-debugger

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.