microsoft / microsoft/vscode-python-environments

Expose helper for resolving python-env search paths (getAllExtraSearchPaths)

Aperta
#960 1 commento 0 reazioni 1 assegnatario Vedi su GitHub

@eleanorjboyd ci sta già lavorando.

Dal 11/11/2025.

area-api feature-request help wanted needs PR
Lingua principale
TypeScript
Stelle
138
Fork
62
Merge medio
1g 4h
PR unite (30g)
35

Descrizione

### Summary
Extensions that integrate with ms-python.vscode-python-envs need the canonical list of user-configured search paths. Today that logic lives in src/managers/common/nativePythonFinder.ts#getAllExtraSearchPaths, but it isn’t exposed through the public API, so consumers have to re-implement a fairly large helper.

### What we’d like
Export a function (or add an API surface) that returns the same array of search directories the native finder uses—covering legacy python.venvPath / venvFolders, python-env.globalSearchPaths, workspaceSearchPaths, validation, and relative-path resolution across multi-root workspaces.

### Why
In order to use this for another environment plugin, such as the pixi env manager (https://github.com/renan-r-santos/pixi-code), one would have to copy over that code verbatim so it can stay behaviourally aligned with ms-python.vscode-python-envs. Keeping two copies in sync is brittle; a shared helper would make it much easier to keep the behaviour consistent by default.

Happy to send a PR once there’s agreement on where such an export should live.

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.