add config option to force --always-copy parameter for virtualenv

[finswimmer]

virtualenv uses symlink to the interpreter when creating a venv. While this reduces space and runtime this might lead to unexpected results, when the interpreter to which the symlink points get upgraded.

This PR introduce a config option virtualenvs.options.always-copy. If setting to true the --always-copy parameter is added to virtualenv command on creating the venv.

To keep the current behavior as default, this option is set to false by default.

Pull Request Check List

Resolves: #3134

• Added tests for changed code.
• Updated documentation for changed code.

[abn]

@finswimmer LGTM. Althought, I am wondering if we should names psace this into something like virtualenvs.options.always-copy or smilar. I feel we will have more options to be exposed. Alternatively we can also consider supporting virtualenvs.options.*, boolean beign flags that simply get transfored to --<flag>. This will also enable us to support options like system-site etc.

[finswimmer]

Althought, I am wondering if we should names psace this into something like virtualenvs.options.always-copy or smilar. I feel we will have more options to be exposed.

Yes, this sounds like a good idea.

Alternatively we can also consider supporting virtualenvs.options.*, boolean beign flags that simply get transfored to --.

IMO that's a bit risky. I'm quite sure there will be people, who are able to create a config that will break poetry ;) So, we should carefully choose which flag we want to include.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.