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
Change order of options in "Create Environment" flow when .venv exists in the workspace #22038
Comments
We are reserving this issue for Grace Hopper's Open Source Day, which will take place on September 22nd, 2023. If you're part of the event and would like to submit a contribution to this issue, please let us know, and we'll be happy to assign it to you. For other community members who are not participating in the event, we appreciate your interest in contributing! We kindly request that you wait until after September 22nd to work on this issue. If no one from the event has been assigned to it by then, we'll gladly assign it to you. Thank you for your understanding and support! |
Hi, I'm participating in GHC Open Source Day and would like to work on this issue. Could you please assign it to me? |
@annaburlyaeva done! |
Opened a pr #22055 |
@annaburlyaeva Fix should be out in the pre-release version of the extension in a day, use the following to try it out: |
When there is already a virtual environment called
.venv
in the workspace and you run the "Python: Create Environment" command in VS Code & select "Venv", we show an option to delete the environment or use the existing one:@cwebster-99 received some good feedback in user studies with a suggestion to change the order so "Use" shows before "Delete", as it's more likely folks will want to select the existing one than recreate it.
The text was updated successfully, but these errors were encountered: