forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
area-editor-*User-facing catch-allUser-facing catch-allarea-terminalfeature-requestRequest for new features or functionalityRequest for new features or functionalitygood first issueneeds PRReady to be worked onReady to be worked on
Description
- Have a repo that contains a virtual environment
- Open it but do not open any Python files such that the Python extension is not activated
- Open a terminal
- 🐛 the virtual environment is not activated in the terminal and I have to manually activate the environment
Once the Python extension has activated at least once, it contributes those environment variables to the terminal, and VS Code caches those environment variables, so everything works on subsequent runs. Without that context though, the current behavior feels quite unpredictable. It feels like there is a missing activation event for the Python extension in this scenario. Maybe it could also activate on workspaceContains:.venv?
Metadata
Metadata
Assignees
Labels
area-editor-*User-facing catch-allUser-facing catch-allarea-terminalfeature-requestRequest for new features or functionalityRequest for new features or functionalitygood first issueneeds PRReady to be worked onReady to be worked on