You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Change order of options in "Create Environment" flow when .venv exists in the workspace #22038
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:
Courtney Webster (@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.
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!
changed the title [-]Change order of options in create environment command when there already exists a .venv in the workspace[/-][+]Change order of options in "Create Environment" flow when a .venv already exists in the workspace[/+]on Sep 20, 2023
changed the title [-]Change order of options in "Create Environment" flow when a .venv already exists in the workspace[/-][+]Change order of options in "Create Environment" flow when a .venv exists in the workspace[/+]on Sep 20, 2023
changed the title [-]Change order of options in "Create Environment" flow when a .venv exists in the workspace[/-][+]Change order of options in "Create Environment" flow when .venv exists in the workspace[/+]on Sep 20, 2023
Activity
luabud commentedon Sep 20, 2023
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!
[-]Change order of options in create environment command when there already exists a .venv in the workspace[/-][+]Change order of options in "Create Environment" flow when a .venv already exists in the workspace[/+][-]Change order of options in "Create Environment" flow when a .venv already exists in the workspace[/-][+]Change order of options in "Create Environment" flow when a .venv exists in the workspace[/+][-]Change order of options in "Create Environment" flow when a .venv exists in the workspace[/-][+]Change order of options in "Create Environment" flow when .venv exists in the workspace[/+]annamelbury commentedon Sep 21, 2023
Hi, I'm participating in GHC Open Source Day and would like to work on this issue. Could you please assign it to me?
luabud commentedon Sep 22, 2023
@annaburlyaeva done!
annamelbury commentedon Sep 22, 2023
Opened a pr #22055
Changed order of options in Create Environment flow when .venv exists… (
karrtikr commentedon Sep 22, 2023
@annaburlyaeva Fix should be out in the pre-release version of the extension in a day, use the following to try it out:
Changed order of options in Create Environment flow when .venv exists… (
Merged PR posit-dev/positron-python#224: Merge/2023.18
Merged PR posit-dev/positron-python#224: Merge/2023.18