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

venv from different folder is autoselected #21886

Closed
joyceerhl opened this issue Aug 29, 2023 · 2 comments
Closed

venv from different folder is autoselected #21886

joyceerhl opened this issue Aug 29, 2023 · 2 comments
Assignees
Labels
info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team

Comments

@joyceerhl
Copy link

Testing #21878

  1. Create a folder with a venv, open in VS Code, select that venv via language status bar item (autoselection didn't work)
  2. Create a different folder as a sibling with a different venv, open in VS Code
  3. 🐛 the venv from step 1 was autoselected for the folder from step 2 (in the screenshot below, the venv from step 1 was Python 3.10 and the venv from step 2 was Python 3.11)

Image

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Aug 29, 2023
@karrtikr
Copy link

karrtikr commented Sep 5, 2023

Unfortunately I'm unable to reproduce this on Windows. Here's what I did on my fresh set up:

  • Create folder1 under folders, create a Python file, create a virtual env ".venv" with Python 3.10
  • Create folder2 under folders, create a Python file, create a virtual env ".venv" with Python 3.11
  • Open folder1 as workspace folder, and make sure ".venv" with Python 3.10 is selected
  • Open folder2 as workspace folder, and noticed ".venv" with Python 3.11 is auto-selected

Can you confirm if these are the repro steps?

@github-actions github-actions bot added the info-needed Issue requires more information from poster label Sep 5, 2023
@github-actions
Copy link

github-actions bot commented Oct 6, 2023

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

3 participants