microsoft / microsoft/vscode-python-environments

Support `uv run` as an optional default run action.

Ouverte
#1,281 1 commentaire 47 réactions 2 personnes assignées Voir sur GitHub

@anthonykim1 y travaille déjà.

Depuis le 13/3/2026.

area-environment feature-request help wanted needs community feedback
Langage dominant
TypeScript
Étoiles
138
Forks
62
Merge moyen
1 j 4 h
PR mergées (30 j)
35

Description

Currently, the Run Python File in Terminal play button (and the default python debugger) is hardcoded to run the current python file using the activated environment.

For uv scripts with dependencies this causes an issue.

If it were possible to configure this as a setting to run using uv run ${file} instead, it would allow seamless integration for rust scripts, same for the debugger.

I've come from related issues: https://github.com/astral-sh/uv/issues/8558, https://github.com/astral-sh/uv/issues/7803, and https://github.com/astral-sh/ty-vscode/issues/353, but realised it's not possible to implement this feature anywhere other than the vscode-python repo.

Debugging can work with a custom launch.json specifying uv run --with-requirments ${file} python, but this has the caveat that it will fail for scripts with no inline dependencies defined. Being able to use just uv run as the actual command would allow it to always work. Though my guess is this requires work on debugpy itself to better support uv.

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.