Skip to content
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

${env:<VARIABLE>} substitution is no longer working for .env files #20211

Open
karrtikr opened this issue Nov 11, 2022 · 4 comments
Open

${env:<VARIABLE>} substitution is no longer working for .env files #20211

karrtikr opened this issue Nov 11, 2022 · 4 comments
Assignees
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug debt Covers everything internal: CI, testing, refactoring of the codebase, etc. needs PR Ready to be worked on

Comments

@karrtikr
Copy link

We document it so it should work: https://code.visualstudio.com/docs/python/environments#_variable-substitution

@karrtikr karrtikr added bug Issue identified by VS Code Team member as probable bug debt Covers everything internal: CI, testing, refactoring of the codebase, etc. area-environments Features relating to handling interpreter environments needs PR Ready to be worked on labels Nov 11, 2022
@karrtikr karrtikr self-assigned this Nov 11, 2022
@luabud
Copy link
Member

luabud commented Jan 10, 2023

Dupe of microsoft/vscode-python-debugger#523?

@luabud
Copy link
Member

luabud commented Jan 10, 2023

in any case, I'm removing the support from the docs until we fix this :)

@karrtikr
Copy link
Author

Dupe of microsoft/vscode-python-debugger#523?

Actually that issue is only for debugger, the issue is sometimes ${env: is needed and sometimes its not. So i think we should keep both open.

@karrtikr karrtikr removed their assignment Oct 26, 2023
@eleanorjboyd
Copy link
Member

@paulacamargo25 is this still relevant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug debt Covers everything internal: CI, testing, refactoring of the codebase, etc. needs PR Ready to be worked on
Projects
None yet
Development

No branches or pull requests

5 participants