Skip to content
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

Conda interpreters type not being determined #10886

Closed
karrtikr opened this issue Mar 31, 2020 · 2 comments
Closed

Conda interpreters type not being determined #10886

karrtikr opened this issue Mar 31, 2020 · 2 comments
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@karrtikr
Copy link

karrtikr commented Mar 31, 2020

In https://github.com/Microsoft/vscode-python/blob/7c81cfcd06cdbfd91224489864ac3c9ae2c16d59/src/client/interpreter/virtualEnvs/index.ts#L50,

We determine the type of the interpreter user has set in the settings. It looks we don't bother determining whether this is a conda environment or not, which means even if the interpreter type is Conda, it's being interpreted as Unknown type.

cc @luabud

@karrtikr karrtikr added bug Issue identified by VS Code Team member as probable bug needs PR area-environments Features relating to handling interpreter environments labels Mar 31, 2020
@luabud
Copy link
Member

luabud commented Feb 16, 2021

This is something we should monitor as we roll out #12020

@karrtikr
Copy link
Author

This is now fixed.

@karrtikr karrtikr added this to the October 2021 milestone Oct 22, 2021
@karrtikr karrtikr added the verified Verification succeeded label Oct 25, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants