Provide standardized way on how env variables override .env

Environment data

• VS Code version: 1.23.1
• Extension version (available under the Extensions sidebar): 2018.4.0
• OS and version: 10.12.6
• Python version (& distribution if applicable, e.g. Anaconda): 3.6.5
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): venv

Actual behavior

envFile variables override launch.json env variables

Expected behavior

launch.json env variables override envFile variables

Steps to reproduce:

• Define envFile with a variable
• Define an env variable in launch.json with the same name
• Run a script

[WeetA34]

Hello,

In official VSCode Debug Node.js documentation, we can see that env variables override envFile variables (Any environment variable specified in the env dictionary will override variables loaded from the file.).

In Python, it’s the opposite. I didn’t find something which describes the behavior in the documentation. It’s a bit confusing to have a different precedence compared to another language (ie. Node.js). Is-it possible, at least, to put the variables precedence described here in the documentation?

Thx

[luabud]

Thanks from bringing it up @WeetA34, I created https://github.com/microsoft/vscode-docs/issues/3674 so we can clarify that in our documentation.

We might need to revisit how we handle this in the extension as well.