Description:

The default configuration example for #281's new example installs poetry before actions/setup-python is ran.

This can run into some funky issues in poetry itself since poetry may stick to use the python version it was installed in.

This may be on the poetry side. I'm not sure:

• Oldest post I could find (closed): Poetry using the wrong Python version (not related to pyenv) python-poetry/poetry#655
• Poetry uses wrong Python version python-poetry/poetry#4101
• See if in 1.2.x prerelease PR helps: Add (experimental) option to use current active python to create venv ("pyenv way") python-poetry/poetry#4852: Seems not to https://github.com/tony/setup-python-poetry-version-example/blob/main/.github/workflows/experiment-with-poetry-prerelease.yml

Action version:
v3.1

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:

Repro steps:
Reproduction repo: https://github.com/tony/setup-python-poetry-version-example

• https://github.com/tony/setup-python-poetry-version-example/tree/main/.github/workflows

  • default-example.yml
  • default-example-install-poetry.yml
  • experiment-with-poetry-prerelease.yml
  • workaround.yml by trigger poetry env use <version> to force version

Runs: https://github.com/tony/setup-python-poetry-version-example/actions

Expected behavior:
poetry should respect the version in actions/setup-python

Actual behavior:
It uses the python version poetry was installed with before actions/setup-python was ran.