Concept of global virtual environment is a bit confusing

[cwebster-99]

Currently if there is no folder/workspace open in VS Code we allow users to create a virtual environment if they select a folder to create a "global virtual environment". We then create an environment and select it as such, but we do not open the folder where the environment is created. Should we open that folder?

[eleanorjboyd]

should we even allow someone to create a venv if they are not in a workspace? @karthiknadig

[cwebster-99]

I like the flow where someone can select a folder/workspace for the venv to be created rather than failing out of the flow. I would just expect that after the user selects the folder for the venv creation that it also opens that folder in VS Code

[eleanorjboyd]

I just cant open a new folder then trigger actions again... I forgot. Ok let me see what I can do

[cwebster-99]

Discussed offline that we will just open the selected folder and trigger environment creation after so the end result is > Folder opened in the editor and newly created environment added