Delay Python environment discovery until the extension is used

[Vipitis]

Currently the extension tries to discover all python enviornments when it's activated. Meaning every time you start VSCode, or when you switch worksapces etc. Even if you don't intent to use Marimo this session.

Please change this behaviour or at least make it configurable. Otherwise I will continue to disable the extension untill I need it - which is really awful user experience. Especially since it doesn't correctly discover virtual enviornments or let's us manually specify a path (I think there already exists issues for this, let me know if I should find and link them or file more).

A solution could be something like rust-analyzer which let's you configure any kind of startup load:

[manzt]

Thanks for opening the issue. We likely need to explore other lifecycle hooks for activation.

[Vipitis]

I did manage to cut a large part of the startup delay by disabling the first party python environments extension. Perhaps there was some kind of conflict?

I am not too familiar with how VSCode handles it, but when "select a kernel" inside the notebook - why can't it be the same as "select interpreter"? Which also lets me manually give the path to a managed env should the discovery fail?