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

Creating new venv, recommended tag #23858

Open
eleanorjboyd opened this issue Jul 23, 2024 · 1 comment
Open

Creating new venv, recommended tag #23858

eleanorjboyd opened this issue Jul 23, 2024 · 1 comment
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug needs PR Ready to be worked on

Comments

@eleanorjboyd
Copy link
Member

Testing #23848

  1. open select interpreter
  2. create new venv from terminal python3.10 -m venv myenv23
  3. the new env will appear in the select interpreter at the bottom
  4. exit the picker, go to select interpreter again
  5. now the venv is listed as recommended and wasn't before

This flow just feels weird to me because I would want consistency in terms of where to find the venv for the workspace folder. Sometimes it is at the very top, since it is recommended, or at the very bottom. Also saying it is recommended when I restart the quickpick but not on refresh might be confusing
Screenshot 2024-07-23 at 10 22 25 AM
Screenshot 2024-07-23 at 10 22 15 AM

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Jul 23, 2024
@karthiknadig
Copy link
Member

I agree with this assessment. This is an issue with the picker and not with the native detection.

@karthiknadig karthiknadig removed their assignment Jul 23, 2024
@karthiknadig karthiknadig added bug Issue identified by VS Code Team member as probable bug area-environments Features relating to handling interpreter environments needs PR Ready to be worked on and removed triage-needed Needs assignment to the proper sub-team labels Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug needs PR Ready to be worked on
Projects
None yet
Development

No branches or pull requests

2 participants