forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
area-terminalbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugexperimentingFeature is part of an experimentFeature is part of an experimentverifiedVerification succeededVerification succeeded
Milestone
Description
Workaround
This is a known issue, see #22037 (comment) for a workaround in bash.
Expected vs. Actual
Expected: running deactivate exits the venv in that particular shell context
Actual: running deactivate shows command isn't found
(data-loader-prototype-py3.10) [admin-smiller@UUE2OLY01L olympus]$ deactivate
bash: deactivate: command not found
Behaviour
I would expect the environment to be properly sourced in my bash shell context. Instead commands like "deactivate" are not found given the inital shell context.
Steps to reproduce:
- Select a python interpreter via the python plugin
- Open an new terminal
- Try deactivating the default environment
nicklausd and EmporioSabo
Metadata
Metadata
Assignees
Labels
area-terminalbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugexperimentingFeature is part of an experimentFeature is part of an experimentverifiedVerification succeededVerification succeeded