Skip to content

Autoactivation of virtual environment in vscode doesnt trigger eventhough notification pops up #247168

@Ethanshibu

Description

@Ethanshibu

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.99.3
  • OS Version: windows 11 pro kernel 10.0.26100

Steps to Reproduce:

  1. create a virtual env using python -m venv venv in a vscode terminal in your project folder.
  2. close the terminal or the window itself.
  3. reopen the terminal and wait. The notification pops up saying that venv was activated eventhough venv isnt written in the powershell prompt.

To test my suspicion I entered pip list. if venv is not activated, it would list all pip installed files in my system. if its active then it wont show anything or maybe the installed packages in that folder/venv. it showed the system packages. to confirm my suspicion i activate the env and pip list again. then it only showed my flask and sqlalchemy coz those were the only packages I installed in the venv.
is this a valid issue? i ended up installing torch in my system and it took alot more space than i thought. it also created conflicts with other files.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions