VS Code python.envFile does not seem to work with python.defaultInterpreterPath

[sugatoray]

Despite specifying a python.envFile in workspace (.vscode/settings.json), python.defaultInterpreterPath does not seem to fetch the interpreter path via an environment variable, declared in the envFile.

# filename: .env
# set this in .vscode/settings.json:
# "python.envFile": "${workspaceFolder}/.env"
DEFAULT_INTERPRETER_PATH=path/to/python/interepreter

// filename: .vscode/settings.json
{
    "python.envFile": "${workspaceFolder}/.env",
    "python.defaultInterpreterPath": "${env:DEFAULT_INTERPRETER_PATH}",
    "python.terminal.activateEnvironment": true,
    "python.terminal.activateEnvInCurrentTerminal": false,
    "jupyter.jupyterServerType": "local",
}

If I hard code the python.defaultInterpreterPath, it works, and auto activates the interpreter, when I open a new terminal window. But it does not activate the the interpreter from the variable (in .env file).

References

• https://code.visualstudio.com/docs/python/environments#_environment-variables
• https://stackoverflow.com/questions/56178143/in-vs-code-debugger-how-do-i-use-envfile-in-launch-json-for-nodejs
• https://www.youtube.com/watch?v=qTU7w3bWrOk&ab_channel=JonathanSoma
• This says you can only use the env variables from the .env file if you are debugging: https://www.reddit.com/r/vscode/comments/tkwooh/run_not_debug_python_using_the_env_file/
• .env file not working on run current file action #11174

🔥 Note

I have raised this as a question on stackoverflow already.

• https://stackoverflow.com/questions/72571271

---

Does this issue occur when all extensions are disabled?: Yes/No

I have not and can't afford to check that as I don't know a programmatic way of restoring current extensions state.

Diagnostics Info:

Version: 1.67.2
Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5
Date: 2022-05-17T18:23:40.286Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Linux x64 5.13.0-44-generic snap

Steps to Reproduce:

Follow the description given above.

---

💡 I have opened another issue here:

• VS Code "python.envFile" does not seem to work with "python.defaultInterpreterPath" vscode#151703 (comment)

I was told to contact with vscode-python by the vscode team.

[brettcannon]

The issue is at #19276 (although in the future please only open one thing, otherwise it splits the conversation and it's hard to track).

This is working as intended. VS Code does not load environment files when evaluating settings and we don't either; environment files are meant for when we execute Python code.

[sugatoray]

I opened only one issue first. But then that issue was closed and I was asked to raise another here.

[sugatoray]

This is working as intended. VS Code does not load environment files when evaluating settings and we don't either; environment files are meant for when we execute Python code.

This does not seem to work if I try opening the following:

• start a new shell (auto activation of python environment)
• add # %% to any line in a python file, making the following section eligible to run in interactive mode: the interactive mode cannot auto start with the correct python interpreter.

Both these seem to work only when I hard code the python interpreter path in .vscode/settings.json.

The documentation says that for python.defaultInterpreterPath if you use a variable from the .env file, it should work. That's precisely the example of using a variable from the .env file.

[brettcannon]

The documentation says that for python.defaultInterpreterPath if you use a variable from the .env file, it should work. That's precisely the example of using a variable from the .env file.

And that's a mistake. Can you tell me where you found that in our documentation?

[brettcannon]

/cc @karrtikr

[sugatoray]

Hi @brettcannon,

And that's a mistake. Can you tell me where you found that in our documentation?

Here it is. Source: https://code.visualstudio.com/docs/python/environments#_manually-specify-an-interpreter

On a different note

This is confusing! In the last two lines, it says:

But then again, here it seems that you could in fact use variable substitution in a .env file?!
I am not clear on what is a definitions file.

cc: @karrtikr

[brettcannon]

I've opened microsoft/vscode-docs#5413 to clarify the documentation.

[sugatoray]

This could be related:

• Use environment variables defined in .env file when running code in a terminal #944