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

Editing .env file requires restarting of vscode to detect new values #183

Closed
DonJayamanne opened this issue Nov 14, 2017 · 1 comment · Fixed by #466
Closed

Editing .env file requires restarting of vscode to detect new values #183

DonJayamanne opened this issue Nov 14, 2017 · 1 comment · Fixed by #466
Labels
feature-request Request for new features or functionality
Milestone

Comments

@DonJayamanne
Copy link

From @DonJayamanne on September 21, 2017 23:34

This would impact environment variables used by unittests and debugged code.

Copied from original issue: DonJayamanne/pythonVSCode#1230

@DonJayamanne
Copy link
Author

Removed from October milestone as this hasn't been reported yet.

@brettcannon brettcannon added awaiting 1-decision feature-request Request for new features or functionality labels Nov 14, 2017
@brettcannon brettcannon mentioned this issue Nov 29, 2017
10 tasks
DonJayamanne added a commit that referenced this issue Jan 3, 2018
Refactor how environment variables are parsed and used in tools, language server and debugger

Fixes #316 (PYTHONPATH not used as extra path for auto complete)
Fixes #183 (changes to .env file requires restarts of vscode)
Fixes #436 (Path variables not inherited when debugging)
Fixes #435 (Virtual environment name is same as the default environment file)
@brettcannon brettcannon added this to the January 2018 milestone Jan 3, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants