Indicate to the user about any conda envs lacking an interpreter which do not use a valid python binary

[greazer]

Version: 1.67.0-insider (user setup)
Commit: a9288be
Date: 2022-04-15T05:16:11.219Z
Electron: 17.4.0
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Windows_NT x64 10.0.22593

Python (pre-release): v2022.5.11051003

Here's my conda env list:

Here's the Select Interpreter list:

Here's the log
MissingEnvironments.txt

[karrtikr]

@greazer Apologies for the issue, does this work in the stable release of the extension?

Unfortunately the logs aren't verbose enough atm, so I will soon create a new VSIX and post it here for you to try out.

[karrtikr]

Here's the VSIX: https://github.com/microsoft/vscode-python/suites/6162882956/artifacts/215887730, please provide the logs again.

EDIT:

We discussed offline that the above VSIX fixes the bug, here's the log:

MissingEnvironments2.txt

[karrtikr]

However some of envs are invalid in the sense they do not contain a valid python binary. So they do not appear in the list.

Error: Command failed: C:\Users\jimg\anaconda3\Scripts\conda.exe run -n jupyter-lab-test-env --no-capture-output --live-stream python c:\Users\jimg\.vscode-insiders\extensions\ms-python.python-2022.5.2185428346-dev\pythonFiles\get_output_via_markers.py -c "import sys;print(sys.executable)"
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases.

It would be nice to somehow indicate this to the user that we did discover these so the conda env list matches with what the extension shows. Turning this into a feature request. This means we either:

• Add support for selecting (and possibly fixing these envs).
• Somehow indicate in the interpreter list that these envs are invalid.
• Showing a notification on discovery, or even popping up a dialog box if the user happens to pick an invalid kernel, stating that it can't be used.

Blockers:

• Internally it is always assumed an environment has an executable.
• We currently validate all envs before displaying them in the list, make sure we skip any type of validation for these envs as they do not have a python binary we can run.