@bitter-ability-32190 is there any way to disable/opt-out of the pyenv provider per environment? I'd like to use it for

local_environment

but if using a

docker_environment

I'm happy to setup the Python to use in the image before hand, as it otherwise needs to install the Python every time the image boots up (it seems, not sure, as the install failed in the image I tried with..)

I'm not 100% but I think if you forked the plugin locally you could have the top-level rule choose whether to setup and run pyenv or pass it on to the next impl

Is there an option which disables / enables pyenv? And if so, can it be customized per environment as other options are customized per environment?

FWIW I'd like to be able to control "which python getter to use" per Python version... or maybe per target?

I'm sure, with changes/proposals to the infra, any and all of these are possible. The hard part is simply the design+UI/UX

I can take a stab at it..