Remote python interpretrer no longer detected or applied

[risbochris]

Issue Type: Bug

Python interpreters on remote conda envs no longer discoverd or applied when selected. CTRL + SHIFT + P -> Select Python Interpreter -> Select one -> Nothing is applied on the project environnement.

Since last version of VSCode : 1.65.2

VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:55.248Z) OS version: Windows_NT x64 10.0.19044 Restricted Mode: No Remote OS version: Linux x64 4.15.0-1113-azure

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)| |GPU Status|2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|31.84GB (17.67GB free)| |Process Argv|--crash-reporter-id 8b81856c-47d1-4bbf-8db8-1936293d5797| |Screen Reader|no| |VM|0%| |Item|Value| |---|---| |Remote|SSH: DSVM| |OS|Linux x64 4.15.0-1113-azure| |CPUs|Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz (16 x 2294)| |Memory (System)|251.91GB (165.90GB free)| |VM|0%|

Extensions (39)

Extension|Author (truncated)|Version ---|---|--- theme-monokai-pro-vscode|mon|1.1.20 vscode-language-pack-fr|MS-|1.65.3 jupyter-keymap|ms-|1.0.0 remote-ssh|ms-|0.76.1 remote-ssh-edit|ms-|0.76.1 material-icon-theme|PKi|4.14.1 ayu|tea|1.0.5 vscode-icons|vsc|11.10.0 swagger-viewer|Arj|3.1.2 gitlens|eam|12.0.5 scriptcsRunner|fil|0.1.0 code-runner|for|0.11.7 Python-autopep8|him|1.0.2 sftp|lix|1.12.10 vscode-azureappservice|ms-|0.23.1 vscode-azurelogicapps|ms-|1.0.12 vscode-azureresourcegroups|ms-|0.4.0 vscode-docker|ms-|1.21.0 vscode-logicapps|ms-|1.1.3 vscode-language-pack-fr|MS-|1.65.3 vscode-dotnet-runtime|ms-|1.5.0 data-workspace-vscode|ms-|0.1.1 mssql|ms-|1.13.0 sql-database-projects-vscode|ms-|0.14.1 python|ms-|2022.2.1924087327 vscode-pylance|ms-|2022.3.3 jupyter|ms-|2022.2.1030672458 jupyter-keymap|ms-|1.0.0 jupyter-renderers|ms-|1.0.6 azure-account|ms-|0.10.1 powershell|ms-|2021.12.0 azurerm-vscode-tools|msa|0.15.6 autodocstring|njp|0.6.1 vscode-commons|red|0.0.6 vscode-yaml|red|1.5.1 file-tree-generator|Shi|1.1.1 docker|vsc|1.0.0 sql|vsc|1.0.0 yaml|vsc|1.0.0 (1 theme extensions excluded)

A/B Experiments

``` vsliv368cf:30146710 vsreu685:30147344 python383cf:30185419 vspor879:30202332 vspor708:30202333 vspor363:30204092 pythonvspyl392:30443607 pythontb:30283811 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 vscoreces:30445986 pythondataviewer:30285071 vscod805:30301674 pythonvspyt200:30340761 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 vsaa593cf:30376535 vsc1dst:30438360 pythonvs932:30410667 wslgetstarted:30449410 vsclayoutctrt:30451275 dsvsc009:30452663 pythonvsnew555:30457759 vscscmwlcmt:30438805 pynewfile477cf:30450039 ```

[karrtikr]

Nothing is applied on the project environnement.

Note we no longer display the selected interpreter in the status bar, so maybe that's why you feel nothing is applied: https://github.com/microsoft/vscode-python/issues/18283

Please provide the logs after selecting an interpreter:

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

``` XXX ```

[jlcarmic]

I have also experienced this problem. Previously I had the following in my settings:

"python.defaultInterpreterPath": "udngatewaydev/bin/python2.7",

This resulted in a no folder found message in Output. I changed it to:

"python.defaultInterpreterPath": "${workspaceRoot}/udngatewaydev/bin/python2.7",

The behavior has not changed, I still have a warning about no interpreter selected, but now there is nothing in Output.

[jlcarmic]

Update: For me this was actually related to the fact that we're still using Python 2.7 and Apple has removed it from the system with Monterey 12.3. So it's not a VS Code issue, it's my system not having Python anymore. Once I updated my system, VS Code went back to behaving correctly.

[brettcannon]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.