-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Variable substitution not working in environment variable definitions file when debugging #523
Comments
@martinResearch, thanks for letting us know about this. Currently when you provide the "envFile" setting to the debugger, the extension only applies to that .env file the env vars defined in the "env" setting. Process-defined and other extension-defined env vars are not used. We'll check on what can be done about that and get back to you. |
See: src/client/debugger/extension/configuration/resolvers/helper.ts |
For me it seems to actually work, if i skip
|
Still happening when using 2021.4.681399556-dev. |
Hi! Since it has been a year or so since this was last updated I wanted to check in to see if this issue still persists. Let me know if so, and any updated information you can provide and ill take a look! Thanks |
Environment data
VS Code version: 1.52.0
Extension version (available under the Extensions sidebar): v2020.11.371526539
OS and version: Windows 10 Enterprise 20H2
Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:58:18) [MSC v.1900 64 bit (AMD64)] on win32
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Expected behaviour
Should print the content of the PATH environment variable
Actual behaviour
the string "${env:PATH};" get printed
Steps to reproduce:
Steps to Reproduce:
create these files
d:\repos\bug_vscode\test.py:
d:\repos\bug_vscode.vscode.env
d:\repos\bug_vscode.vscode\launch.json
launch with the debug configuration from the GUI
This produces these prints in the terminal:
while, according to the documentation here I would expect
${env:PATH}
to be replaced by the content of the environment variableDocumented the issue here microsoft/vscode#112142 but got closed assuming it was a problem with the extension
The text was updated successfully, but these errors were encountered: