Skip to content

API not listing conda env with the same interpreter path #18736

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DonJayamanne opened this issue Mar 21, 2022 · 7 comments
Closed

API not listing conda env with the same interpreter path #18736

DonJayamanne opened this issue Mar 21, 2022 · 7 comments
Assignees

Comments

@DonJayamanne
Copy link

DonJayamanne commented Mar 21, 2022

Testing #18727

@karrtikr I cannot test the API

  • Installed pre-release (that didnt work, it doesn't have the new methods)
  • I created a VSIX locally from dev (because of the previous not being available in marketplace).

Here's the code

        const interpreters = await pythonExt?.exports.environment.getEnvironmentPaths();
        const tests = interpreters?.filter(item => item.path.endsWith('test1') || item.path.endsWith('test2'));

However in dev version, I cannot get a list of the conda environments without any executables? I.e. it doesn't work

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Mar 21, 2022
@DonJayamanne
Copy link
Author

False alarm, I hadn't updated my condaPath correctly

@DonJayamanne
Copy link
Author

Also, when I use the command Select Interpreter I cannot see the conda environments test1 and test2 (these are teh conda envs created as per the test plan).

Basically i cannot select conda envs with the same interpreter path

@karrtikr
Copy link

It seems pre-release doesn't seem to carry the latest insiders build of the extension. cc/ @karthiknadig Is pre-release only supposed to be updated once a day?

Please try the VSIX from the latest build: https://github.com/microsoft/vscode-python/suites/5743881227/artifacts/190539612

@karthiknadig
Copy link
Member

karthiknadig commented Mar 21, 2022

Pre-release builds happen and publish once at 2:00AM mon-fri

@DonJayamanne

This comment was marked as resolved.

@DonJayamanne

This comment was marked as resolved.

@karrtikr
Copy link

Closing as a non-issue for now.

@karthiknadig karthiknadig removed the triage-needed Needs assignment to the proper sub-team label Mar 22, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants