Experiment with replacing ‘create venv’ with ‘quick create’

[DonJayamanne]

As the title says
Perhaps rename ‘quick create’ to ‘create venv’
It’s feels that to have both, if one is faster then why have the other

Perhaps have a different title when both are enabled so user knows when and why to use the older option

[karthiknadig]

@luabud @cwebster-99 I would like your opinion on this. Also, this could be an experiment with a setting that enables the custom venv. This way the Experiment can control the default, and there will always be a way to keep it on.

Another condition, If there is only one global Python env then why need custom option.

[cwebster-99]

Is this feedback pertaining to this view?

If so, I might suggest that instead of showing venv and conda as top level options that the menu shows "Quick Create" and "Customize" where customize would then direct the user to choosing between managers. We would like to keep another option other than just quick create since users may want to create more than one environment or decide they don't want our opinionated approach.

[eleanorjboyd]

@DonJayamanne do you remember what you mean here? If you could clarify your thoughts on that menu and what you are suggesting then I can look into implementing it

[github-actions]

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!