Skip to content

Wrong python selected after select interpreter #25061

@lorenzomammana

Description

@lorenzomammana

Does this issue occur when all extensions are disabled?: Yes, partially I'm using remote development so I can't really disable that extension, this issue does not seem to arise when running in a wsl.

  • VS Code Version: 1.100.0
  • OS Version: Ubuntu 22.04.5 LTS (docker container)

Steps to Reproduce:

  1. Attach to a remote container
  2. Setup an environment (we use conda, e.g. conda create -n test python=3.10)
  3. Select interpreter -> Select the new environment

  4. which python -> To us it shows /opt/conda/bin/python, which is not the one used for the environment, the environment still looks activated, there's (test) before the username
  5. Run conda activate test manually
  6. which python -> $HOME/.conda/envs/test/bin/python, this is the what happend using vscode < 1.100.0

This is quite problematic as it seems that an environment is active when it's not causing missing dependencies etc..

Metadata

Metadata

Assignees

Labels

triage-neededNeeds assignment to the proper sub-team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions