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

Virtual environment still in interpreter list after being deleted. #7132

Closed
ericsnowcurrently opened this issue Aug 28, 2019 · 1 comment
Closed
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality needs PR Ready to be worked on

Comments

@ericsnowcurrently
Copy link
Member

(using the latest nightly build of the extension)

The extension notices when I've created a new virtual environment. It should also notice when I've deleted that virtual environment (and forget it). Currently it does not.

steps:

  1. verify there are only "system" Pythons in the interpreter list (click on Python version in status bar to see available interpreters)
  2. in the workspace root, run python3 -m venv .venv
  3. verify the new virtual environment is in the interpreter list
  4. delete the ".venv" directory created in step 2
  5. check the interpreter list to see if the virtual environment is still there (it still is)
@karrtikr
Copy link

Closing as this happens because VSCode watcher doesn't fire event as designed.

@karrtikr karrtikr closed this as not planned Won't fix, can't repro, duplicate, stale Dec 14, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-environments Features relating to handling interpreter environments feature-request Request for new features or functionality needs PR Ready to be worked on
Projects
None yet
Development

No branches or pull requests

4 participants