Create environments automatically (or via UI command)

[grst]

When selecting hatch environment that exists in the env matrix, but hasn't been created yet via "Select Interpreter" in vscode, nothing happens.

IMO there should be either
(1) a prompt "This env does not exist, do you want to create it now?", or
(2) an error message "This env does not exist, please create it using ..."

where ... should be a command from the command palette.

[flying-sheep]

I had trouble parsing that sentence. You mean this right?

When using the Select Interpreter command in VS Code to select a Hatch environment that hasn't been created yet, nothing happens.

If so, yeah, that’s certainly a gotcha. If I understood the vscode-python-environments people correctly, the Select Interpreter command interacts with the legacy “global environment”, while selecting an environment in the vscode-python-environments sidebar selects a “workspace environment” (and triggers a Hatch env sync). But that doesn’t explain that VS Code also remembers which global environment each project has?

That confusion is why I filed microsoft/vscode-python-environments#1485 and didn’t try to integrate with the global environment yet. @eleanorjboyd could you maybe help us out here?

[grst]

I wasn't even aware that a vscode-python-environment sidebar exists 👀