microsoft / microsoft/vscode-python-environments

Extension support for environment managers

Offen
#79 15 Kommentare 4 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

feature-request help wanted meta
Vorherrschende Sprache
TypeScript
Sterne
138
Forks
62
Ø Merge
1 T. 4 Std.
Gemergte PRs (30 T.)
35

Beschreibung

# Overview

The intent of the Python Environments extension is to enable developers to provide support for their favorite Python environment and package managers by shipping support via its own extension. This extension provides mechanisms for users to interact with environment managers to create, select, and install packages, etc. Your extension will depend on this extension for user interactions, and you can handle the various core features of the environment manager in your extension. This ensures a consistent experience for the user with specific support for each environment manager.

We are looking for community support to build and maintain these extensions!

## APIs

This extension provides a set of APIs for developers to register their own Environment and Package managers. We are also looking for feedback on the APIs. See here for more details: https://github.com/microsoft/vscode-python-environments?tab=readme-ov-file#api-reference-proposed

## Help wanted

### Environment manager

| Env manager | Status |
| --- | --- |
| `venv` | Built-in [1] |
| `conda` | Expecting community extension [2] |
| `poetry` | Expecting community extension |
| `pyenv` | Expecting community extension |
| `pixi` | [In progress](https://github.com/jjjermiah/pixi-vscode) @jjjermiah |
| `hatch` | [In progress](https://github.com/flying-sheep/vscode-hatch) @flying-sheep |
| `pipenv` | Expecting community extension |
| `uv` | Expecting community extension |
| `activaState` | Expecting community extension |

[1]: `venv` (built-in) will use `uv` if available for environment creation, package install and delete.
[2] : We have demo support for `conda` to show case some of the features of the extension. But we are expecting community extension for full featured support (like for example stacked envs in conda)

### Package manager

| Package Manager | Status |
| --- | --- |
| `pip` | Built-in |
| `conda` | Expecting community extension [1] |

[1] : We have demo support for `conda` to show case some of the features of the extension. But we are expecting community extension for full featured support.

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.

Rechercherichtung

Beginne mit der im Issue verlinkten vorgeschlagenen API-Referenz und vergleiche die Tabellen für environment-manager und package-manager. Wähle einen Manager aus und ermittle den vollständigen Support, der über die Registrierungs-APIs erwartet wird; für den Abschluss wäre eine gepflegte Community-Erweiterung erforderlich, aber das Issue nennt keine Repository-Dateien oder Tests.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
python, typescript, vscode
Bereich
developer-experience, tooling
Issue-Typ
Feature
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Ruhig
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

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