You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Clarify that .env files are not read when doing environment variable substitutions in settings for the Python extension #5413
Found via microsoft/vscode-python#19275 (comment) . Essentially the confusion was thinking that something in a .env file could influence a setting, which it cannot.
Hey Brett Cannon (@brettcannon)! Can you shine your expertise to help me understand a little more? Does this note help or would you like me to work on the paragraphs above it? ☺️
The confusion wasn't about environment variables in environment files as much as people thought environment variables from environment files would be available to use in settings. For instance, people wanted to use PYTHON_INSTALL_LOC as defined in a .env file, but we don't support that.
Activity
rjmolyneaux commentedon Jul 13, 2022
Hey Brett Cannon (@brettcannon)! Can you shine your expertise to help me understand a little more? Does this note help or would you like me to work on the paragraphs above it?☺️
brettcannon commentedon Jul 13, 2022
The confusion wasn't about environment variables in environment files as much as people thought environment variables from environment files would be available to use in settings. For instance, people wanted to use
PYTHON_INSTALL_LOCas defined in a.envfile, but we don't support that.rjmolyneaux commentedon Jul 21, 2022
Thank you for the clarification Brett Cannon (@brettcannon)! I merged 5477 for this issue.