python-version-file does not support .tools-versions

[ssbarnea]

Description:

Opposed to setup-nodejs official action, python one is not able to read .tool-versions files to determine the version of python to be used.

Action version:
latest

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Tools version:

Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.

Expected behavior:
A description of what you expected to happen.

Actual behavior:

Be able to make use of .tool-versions files

$ cat .tool-versions
direnv 2.34.0
nodejs 18.19.1
# asdf install task latest
task 3.37.2
yarn 1.22.19
python 3.12.7

[priyagupta108]

Hello @ssbarnea 👋,
Thank you for your report. We will investigate it and come back to you as soon as we have some feedback.

[priya-kinthali]

Hello @ssbarnea 👋,
This request is similar to issue #571. We will consider enhancing the parsing logic for the python-version-file input to include support for .tool-versions files.
We appreciate your feedback and will evaluate this feature for a future enhancement. In the meantime, please feel free to provide any additional details or use cases to help us better understand the impact and prioritize this feature.
Thank you!

[mahabaleshwars]

Hello @ssbarnea,

We’ve added support for the .tool-versions file. You can test and validate the changes using actions/setup-python@main. These changes will be rolled out soon to actions/setup-python@v5.

Feel free to let us know if you encounter any issues or have any feedback!

[mahabaleshwars]

Hello @ssbarnea,
We are closing this issue now as it has been addressed in this PR.
Please feel free to reach out if you need any further assistance.

[samjarrett]

@mahabaleshwars can we please get this released?