Test: Improvements to "No Python interpreter" selected prompts

[karrtikr]

Refs: #17667

• anyOS @isidorn
• anyOS @bamurtaugh

Complexity: 3

Create Issue

---

Requirements:

• Access to a machine with no Python installed, maybe a devcontainer for linux.
• Pre-release version of the Python extension installed

Steps:

Case 1: No Python installed

• Open a Python file, and use button on top right to run it:
  
• Verify the following prompt shows up:
  
• Verify clicking Select Interpreter opens the quickpick saying:
  

Case 2: Invalid Python selected

• Have Python installed.
• Select an invalid interpreter. You can use Python: Select Interpreter command and choose Enter interpreter path... item.
• Verify following prompt shows up on running Python file in this case:
  

Case 3: Invalid Python selected: multiroot scenario with multiple workspace folders opened

• In this case verify the prompt message describes the workspace folder affected:
  

[isidorn]

The devcontainers for linux that I tried all have python installed.
@bamurtaugh @karrtikr is there some container you recommend using for this case that does not have python?

[karrtikr]

@isidorn I'm not sure about that, can you try deleting the path to python binary? You can get path to binary using:

python -c"import sys;print(sys.executable)"
python3 -c"import sys;print(sys.executable)"

and delete or rename the files like #19549 (comment).

[bamurtaugh]

@bamurtaugh @karrtikr is there some container you recommend using for this case that does not have python?

@isidorn I'm thinking our dev container templates have Python in them since their base Linux distro has Python - I've asked our dev containers working group to confirm.

Here's what I've now ultimately done:

• Opened a project in a dev container as the root user in the container
• Used @karrtikr's recommended commands for finding the path to the Python binary
• rm -r python3 in the path from above (which was /usr/bin)
• Now when I run python3 --version I get: bash: /usr/bin/python3: No such file or directory

[bamurtaugh]

@karrtikr Actually as an amendment to above, it looks like I can still run Python files, so removing the folder didn't work. Do you have a recommended command to delete the path to the Python binary?

[karrtikr]

it looks like I can still run Python files

• What is the command being used to run it?
• What is the path to binary that it's using, is that deleted? Use python -c"import sys;print(sys.executable)" to get the full path.

An alternative could be to run Python: Select Interpreter command and delete every binary file listed there.

[isidorn]

I was able to rm all instances of python that were listed in the Python: Select Interpreter command and then test this item. Thanks for help.