microsoft / microsoft/vscode-python-environments
Expose helper for resolving python-env search paths (getAllExtraSearchPaths)
@eleanorjboyd y travaille déjà.
Depuis le 11/11/2025.
- Langage dominant
- TypeScript
- Étoiles
- 138
- Forks
- 62
- Merge moyen
- 1 j 4 h
- PR mergées (30 j)
- 35
Description
### 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.
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Évaluation
Cette issue n'a pas encore été évaluée.