Repository navigation
.env File no longer updates commented variables #936
Description
On the previous release, commenting out a variable in the .env file would prompt the user to reload the terminal and reinject from .env,
but now, commenting out a variable doesn't prompt, nor will the variable update the next time the user is prompted for another change.
Activity
eleanorjboyd commentedon Oct 13, 2025
To confirm you have the setting "python.useEnvFile" set to true right?
solman252 commentedon Oct 13, 2025
Correct,
in my .vscode/settings.json:
{
"python.terminal.useEnvFile": true,
"python.envFile": "${workspaceFolder}/.env"
}
eleanorjboyd commentedon Oct 14, 2025
what do you have for
terminal.integrated.shellIntegration.enabled? Wondering if Anthony Kim (@anthonykim1) would have any ideas eithersolman252 commentedon Oct 14, 2025
Doesn't show under either my workspace or user settings.json, but in the UI settings it shows as enabled.
anthonykim1 commentedon Oct 14, 2025
I dont remember us supporting
solman252 commentedon Oct 14, 2025
Supporting commented vars? I assure you, there is support for that in both the current and previous releases.
I've attatched a video showcasing the previous behavior in v1.8.0, and the problematic behavior in v1.10.0.
(I had to zip it because you can't attach videos directly on Github, plus I also attatched the workspace folder)
I forgot to showcase it in the video, but closing the terminal and reopening it manually also does not fix the issue, and the environment variable seems to be cached.
Environment Test.zip
Fix issue where terminal environment variables are not removed when t…