Closed osya closed 6 years ago
Lol, looks like we'll need to reopen the VSCode issue as this is an upstream issue. I'll confirm this and reopen that issue, as the SET environment variables statement is generated by VSCode and not the Python extension.
Environment data
Actual behavior
When you use .env file in the VS Code project and CMD.exe as terminal (
"terminal.integrated.shell.windows": "cmd.exe"
) then for settings environment variables generated commands such ascmd /C "set "SECRET_KEY=uh_p8w$eo6%%tf5)d43b2y))88qxf2t9-s=osvq46u#3ya^p+"
without escaping special symbols.Expected behavior
Special symbols (such as
&
and^
) in the values of environment variables from the.env
file in theset
command should be escaped with the^
symbol.Steps to reproduce:
SECRET_KEY=uh_p8w$eo6%%tf5)d43b2y))88qxf2&t9-s=osvq46u#3ya^p+
"envFile": "${workspaceFolder}/.env"
in it (.env file used by default, so may be adding this line is not necessary)Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
)