Any way to set a relative interpreter path for a project, and make it stick?

[pmolodo]

tl;dr - I want to be able to force the python interpreter for a workspace, and not rely on vscode-python's guesses

I have a situation where I have a venv for a workspace, always located at the same location to the workspace. Unfortunately, it's not at a "standard" location (ie, .venv), so I have to manually add it as an interpreter.

This will work initially, but it frequently gets changed to something else - in my case, I often use conda, and if I happen to launch vscode from a terminal that has an activated conda environment, vscode tries to be "smart" and guess that I want to use the conda interpreter. Even worse, this then gets saved as the interpreter for that workspace from then on.

Is there a way to "force" the interpreter to, ie, "${workspaceFolder}/weirdly_named_venv" in the workspace settings.json, and never have it overridden? python.defaultInterpreterPath is only used if no interpreter has ever been selected before, so isn't useful here.

Alternatively, any way to disable automatically setting the interpreter (and permanently saving it) because I happen to launch from a conda activated terminal?

[brettcannon]

I don't believe we have a setting for this, so please feel free to open a feature request for such a setting.