-
Notifications
You must be signed in to change notification settings - Fork 589
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
pythonLocation no longer being set in v4 #537
Comments
Hello @shadycuz! Thank you for reporting this! |
Hello @shadycuz You should point out some:
This build (with python-version:) shows the the pipeline fixed: https://github.com/akv-demo/setup-python-test/actions/runs/3495220045/jobs/5851739586#step:5:14 And this build (without python-version:) repros the issues: https://github.com/akv-demo/setup-python-test/actions/runs/3495204909/jobs/5851706555#step:5:16 Please confirm the answer solves the issue. |
@dsame But I used to not have to manually specify Edit: your own experiment seems to show that it worked in |
Hello @shadycuz. It is an expected behaviour because in v3 tag the action had default value for python-version input. It was removed in scope of this pull request. |
Alright alright, I read throught the I don't really like this change, but I guess its time I use the python version file. |
Description:
When upgrading from
setup-python@v3
tosetup-python@v4
, other jobs fail becauseenv.pythonLocation
is no longer being set.Action version:
v4
Platform:
Runner type:
Tools version:
all?
Repro steps:
Here is the PR. Here is the failed build.
Expected behavior:
python location to be available.
Actual behavior:
It appears to be empty.
Here is the code that now fails with
v4
.The text was updated successfully, but these errors were encountered: