env file not loaded if specified in launch.json and python.envFile

Environment data

• VS Code version: 1.38.0
• Extension version (available under the Extensions sidebar): 2019.9.34474
• OS and version: MAC OS Mojave - 10.14.6
• Python version (& distribution if applicable, e.g. Anaconda): Pyhton 3.7.2 - 64 bit
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): N/A
• Relevant/affected Python packages and their versions: XXX
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): Language Server

Issue description

In the latest build, when debugging a python file using integrated terminal, the contents of “.env” file are not being loaded. This issue is not seen in 2019.8.0. I downgraded to verify that this is a regression issue. Content of launch.json file

        {
            "name": "Python: Terminal (integrated)",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "envFile": "${workspaceRoot}/.env"
        },

Contents of .env file

PYTHONPATH=/opt/library/python:/opt/lib/PythonApi
TCLLIBPATH="/opt/library /Library/Tcl/teapot/package/macosx10.5-i386-x86_64/lib"

[DonJayamanne]

I have submitted a PR to resolve this issue.

[martinstein]

So if envFile in the launch configuration is no longer supported, that means there is no easy way to switch between different env-files for different launch configurations anymore? That feature was very helpful, and it’s even nicely documented here: https://code.visualstudio.com/docs/python/environments#_environment-variable-definitions-file :

A debug configuration also contains an envFile property that also defaults to the .env file in the current workspace (see Debugging - Set configuration options). This property allows you to easily set variables for debugging purposes that replace variables specified in the default .env file

Now you have to go into settings and modify python.envFile each time when you want to run a launch config with a different env-file?

I’m aware of the env option, but that’s not really a good alternative, because it would mean duplicating the values from the env-files.