.env file not parsed properly

[juha-ylikoski]

Type: Bug

This extension will try to load (by default) .env named file (setting ID: python.envFile). This file is not properly parsed.

Steps to reproduce

1. create file .env with content:

KEY="subkey1=subvalue1,subkey2=subvalue2"

2. Select a python interpreter (not sure if necessary)
3. Open a new integrated terminal (terminal>>new terminal). This opens a new terminal and uses the selected python interpreter there as env (e.g. with .venv sources the activate from the .venv folder)
4. run

$ echo $KEY
subkey1

This prints only the first part of the value of the "KEY" environment variable

Expected behavior

Environment variable should be parsed as bash and others parse them. This should cause it to be "subkey1=subvalue1,subkey2=subvalue2"

---

Extension version: 2024.4.1
VS Code version: Code 1.87.1 (1e790d77f81672c49be070e04474901747115651, 2024-03-06T00:21:07.287Z)
OS version: Linux x64 6.5.11-060511-generic
Modes:
Remote OS version: Linux x64 6.5.11-060511-generic
Remote OS version: Linux x64 6.5.11-060511-generic

[anthonykim1]

Thank you for filing this issue! Will investigate this

[anthonykim1]

@juha-ylikoski I'm wondering if this is related to #22982
Can you try adding:
"python.experiments.optOutFrom": ["pythonTerminalEnvVarActivation"] to your settings.json and see if that works?

[juha-ylikoski]

@anthonykim1 I do not seem to be able to reproduce the original bug anymore... Seems that my extension version was updated to 2024.8.1 but after downgrading back to 2024.4.1 I'm still not able to reproduce.

[anthonykim1]

Great, glad to hear.
Please feel free free to reopen/ file issue when you encounter a problem