Add an API to expose the tools such as Conda , PyEnv, etc

[DonJayamanne]

Currenly the Jupyter Extension requires access to the Conda executable hence we have a private API that exposes

• getCondaFile
• getCondaVersion

Ideally just exposing the conda file would suffice, as the version can be derived from the executable.

Similarly I have an ask to expose this in my Python Environment manager, currently I need access to PyEnv, Conda, PipEnv, and other tools.

Given the fact that the tools are exposed in the envs, I think we can look into exposing the executable path as well via some API.

[karrtikr]

Can you clarify on how APIs such as getCondaFile and getCondaVersion being used in Jupyter? Trying to check if an alternative like getActivatedEnvVars() API could potentially solve the problem instead.

[DonJayamanne]

No, that will not be sufficient as we use the conda executable to run conda commands like conda install.
Similarly my personal extensions run other commands like install/uninstall packages.

[eleanorjboyd]

Curious what here has been worked on or if the plan has changed with all the work in environments you have both worked on

[karthiknadig]

There is dedicated API to do package installs, uninstalls, and checks. There is also an api to ask env managers to list installables in the project. APIs to create or remove environments. Those should be sufficient.

See: https://github.com/microsoft/vscode-python-environments?tab=readme-ov-file#api-reference-proposed