Separate installation and initialization in `pyenv_user_install` resource

[tilne]

:person_frowning: Problem Statement

The installation and activation of pyenv_user_install resources is currently inseparable. This makes it impossible to create an environment without also activating it.

❔ Possible Solution

The pyenv_user_install resource should have an attribute (something along the lines of activate?) that can be used to prevent activation of the newly created resource.

[xorima]

Could you PR this new property in with the default being to keep existing behaviour,

At some point in future we should split them out but that is more work

[tilne]

@xorima sure.

[tilne]

Are you still open to the idea of this change? How long would it take from submitting a PR to releasing a new version containing the change?

[xorima]

after merge about 10 mins if myself or another board member.

I don't like waiting for the change to go live.

[MarkGibbons]

Could you explain what you mean by activate a resource? I've mostly seen activate used with regard to virtual environments. The resource does a pyenv init, but so does the installed pyenv.sh script in /etc/profile.d. It's not clear what is wanted here.

[xorima]

My guess @MarkGibbons is that creation of a python environment and activation of that virtual env should be split in some form?

@tilne Can you confirm if I am inline with what you want?