Update placeholder in interpreter picker when selected interpreter changes

[DonJayamanne]

• Install latest pre-release of Python extension
• Open a folder
• I had a .conda folder in this workspace, and then I deleted that (perhaps this was it)
• Go into command to select an python Env
• Select conda
• Select python version 3.9 (I think thats what I selected)
• Wait for creation to complete
• Go into interpreter picker and the newly crated conda env is not found
• Refresh the interpreter picker around 3 times, yet it is not found
• The message also indicates that the interpreter has been selected, but that is not true

Here are screenshots proving the fact taht

• Interpreter was not selected
• Interpreter is not in the list

Here are the logs
logs.txt

[FarukBuldur]

I am not also able to see .venv environment in interpreter picker.

[karrtikr]

Go into interpreter picker and the newly crated conda env is not found

./.conda/bin/python is equivalent to ~/temp/sample2/.conda, which is visible in the list hence it is found. Although the prompt text can be improved here to point to ./.conda/bin/python instead.

• @karthiknadig Please make sure to pass the workspace folder here:

  vscode-python/src/client/pythonEnvironments/creation/createEnvApi.ts

  Line 88 in 7dfa631

  showInformationMessage(`${CreateEnv.informEnvCreation} ${pathUtils.getDisplayName(e.path)}`);

• Regarding "Interpreter was not selected", UI needs to closed and reopened again and you'll notice the interpreter in placeholder is updated.

[karthiknadig]

@karrtikr How do you want it to be shown? In multi root scenario showing ./conda/bin/python is confusing. We had recently discussed that the text we show for select environment can be confusing, especially in multi-root cases.

[karrtikr]

I think it's okay here because that is the environment that was just created for the user, so they will know what that is referring to.

[karthiknadig]

Users can start the process of creating environments for each of their workspaces. In multiroot I would expect them to start creating environments for each of the root.

/cc @luabud @cwebster-99

[karrtikr]

Well they're only going to do it one at a time, so when prompt appears I think they'll know what it represents, even if no path to interpreter is mentioned in the prompt.