Add an option to disable `Create Environment...` button in requirements files

[karthiknadig]

Hi all,

Is there a way to disable this button?

I think this is great for beginners but other users might handle this outside of vscode and the button is distracting.

Originally posted by Daniel Rodriguez (@danielfrg) in #20879 (comment)

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[ppena-LiveData]

I just tested the create a .venv option when I already had one, and it correctly throws an error, so it seems like instead of (or in addition to) an option to disable the button, the code should check to see if an environment is already created for the project and not show the Create Environment... button in that case.

[mcandre]

Meanwhile, disabling the plugin.

[jamesquilty]

I don't usually see floating buttons in the GUI, so the appearance of a Create Environment... button looked like some sort of corruption when I first noticed it — I immediately tried to resolve the issue by quitting and relaunching 😄. It seems to me that context-dependent status and actions are typically shown in the status bar, e.g. Selected Python Interpreter, so I was expecting the Python environment to be handled in the same way.

May I suggest that, instead of a floating button, Create Environment... is integrated into the status bar?

[karthiknadig]

May I suggest that, instead of a floating button, Create Environment... is integrated into the status bar?

/cc Luciana Abud (@luabud) Courtney Webster (@cwebster-99)

[luabud]

I like the idea of adding a setting to disable the button. We likely won't add anything more to the status bar per VS Code extension's UX guidelines

[r-owen]

The button is very distracting and aggressive: the only way to make it go away is to push it, and I know I don't want to create an environment.

[dyve]

Might also help to check if a .python-version exists. The buttons is incredibly annoying.

[nielswadsholt]

The button apparently also hides the "Complete merge" button in the merge editor window 😬

[jerch]

Isnt this something, that can be moved to the right click menu of requirements.txt files? (Pretty much in the sense of "preview" for markdown files...)

I kinda dont get how the current button positioning without any chance to get rid of it got past the UX team. (And yes, I also re-opened vscode twice, as I thought there is a startup bug...)