-
Notifications
You must be signed in to change notification settings - Fork 618
python-version-file
does not support multiple versions
#894
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello @sdimovv, Thank you for creating this issue and we will look into it :) |
Hello @sdimovv, Thank you once again for creating this issue and as per the current implementation, the actions/setup-python action does not support reading multiple Python versions from a .python-version file. Instead, we should specify multiple versions directly in the yaml configuration under the python-version parameter like below as per this documentation.
|
Thank you for your feedback and for highlighting the need for support of multiple Python versions via the python-version-file input. We’re happy to let you know that this feature has now been implemented as part of PR #787. With this update, specifying multiple Python versions in a .python-version file is now supported and works consistently with the python-version input. As this feature request is now fulfilled, we are closing this issue. If you encounter any problems or have further suggestions, please feel free to open a new issue. |
Uh oh!
There was an error while loading. Please reload this page.
Description:
It is possible to specify multiple python versions like so:
However, specifying them like so breaks CI:
.python-version
:Action version:
5
Platform:
Runner type:
Tools version:
Repro steps:
See description
Expected behavior:
Multiple python versions can be read from
.python-version
Actual behavior:
Multiple python versions cannot be read from
.python-version
The text was updated successfully, but these errors were encountered: