Can not select conda Python evironment as Python interpreter

[nahanoo]

Hi,
I open this issue as a follow up of this issue.

When I try to select my conda environment in Python: Select Interpreter. It looks like it's not actually switching the interpreter.
The conda environment I would like select is base (3.12.7) ~/miniconda3/bin/python.
The environment in which the interpreter is "stuck" is Python 3.12.3 /usr/bin/python.

In the example below, plotly is installed only in the base environment.
It looks like it can't find plotly which makes me suspect that the interpreter is not actually changed.

Strangely, in the Select Interpreter menu, the grayed out text is actually correct.

So I'm not exactly sure what's going on but it would useful if my packages would be found again.
I'm on Ubuntu and I installed the pre-release version of Python environments (1.27.10931008) within code-insiders.

Many thanks,

[StellaHuang95]

Thanks for reporting this! I've been investigating but haven't been able to reproduce the issue on my end. Could you help me narrow it down by providing the following information?

After selecting the conda base environment:

1. Settings check
   Open .vscode/settings.json in your workspace and does "python-envs.defaultEnvManager" appear? If so, what value does it have? (It should be "ms-python.python:conda")

2. Status bar
   What does the Python interpreter shown in the bottom-right status bar say? Does it briefly flash to conda base and then revert, or does it never change at all?

3. Extension logs

• Open the Output panel
• Select "Python Environments" from the dropdown
• Set the log level to Debug (use Command Palette → Developer: Set Log Level... → Python Environments → Debug)
• Select the conda base environment again
• Copy and share the full log output

4. Workspace setup
   Is this a single-folder workspace or a multi-root workspace? Do you have any existing python-envs.* or python.defaultInterpreterPath settings in your user or workspace settings?

This might be able to help me pinpoint where the selection is going wrong. Thanks!

[FloHu]

I have the same problem. It started a few weeks ago with vscode simply ignoring the default interpreter setting for a workspace. Now the problem got worse and I run into the popup message "An invalid Python interpreter is selected, please try chaning it to enable features such as IntelliSense (...)".
Interactive work with jupyter is not possible at all anymore as it will stubbornly stick with the base system Python environment and I cannot change the kernel anymore.
The only indication of what may be wrong in the output is
[warning] Unknown environment manager: Mamba

Edit: judging from the reviews and the parent issue this might also be related to the Python Environments (Microsoft) extension, version 1.26.0. However, even after uninstalling the extension I can neither change the interpreter nor change a kernel in the interactive jupyter window.

[eleanorjboyd]

🤖 Thanks for the report. We still need current diagnostics to distinguish this from the earlier reload-only conda bug. Please confirm whether this reproduces on the latest Python and Python Environments releases, then use VS Code's Help: Report Issue flow and share the generated environment details along with trace-level logs from the Python Environments output channel while selecting the environment. Please also include the OS, environment manager and shell, whether this is a single-folder or multi-root workspace, the status-bar interpreter before and after selection, and any python-envs.* or python.defaultInterpreterPath settings. Issues labeled info-needed are automatically closed after 7 days without a reply.