feat(config)!: prefer active python by default

[finswimmer]

From now on Poetry prefers the currently active Python by default. To restore the old behavior the option virtualenvs.use-poetry-python was introduced and must be set to true (default: false).

virtualenvs.prefer-active-python is removed as an option.

[Secrus]

I was actually considering if we could remove that option or invert it so that one can choose to use system Python instead of the active one. That seems more instinctive behaviour than what we have currently

[finswimmer]

I was actually considering if we could remove that option or invert it

I wouldn't remove it, but inverting the default would be fine (But I'm biased here, because that's the config I change first in an new installation ;)

[Secrus]

Well, we could take advantage of the fact that we are making a breaking release and change that to use-system-python that would force usage of the Python version Poetry was installed with. That would give us an open interface to introduce findpython backend without breaking changes but as an alternative (until deemed stable).

[finswimmer]

I'm fine with renaming, but I think use-system-python is confusing for the users. While it is consistent with the code base, I guess most users would expect that the Python of their system is meant. Maybe use-application-python or use-poetry-python?

[Secrus]

I'm fine with renaming, but I think use-system-python is confusing for the users. While it is consistent with the code base, I guess most users would expect that the Python of their system is meant. Maybe use-application-python or use-poetry-python?

I am fine with use-poetry-python and a proper docs entry explaining that.

[github-actions]

Deploy preview for website ready!

✅ Preview
https://website-fcx6j3foz-python-poetry.vercel.app

Built with commit a57ee6c.
This pull request is being automatically deployed with vercel-action

[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.