You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could it also add the PY_PYTHON=<version> on Windows whenever update-environment is true? This will make the default version for the Windows py launcher match the one requested - even if the runner has another version already installed.
Justification:
In short: make sure that py <script.py> runs on the version of python that you just installed with setup-python.
I bumped into this because we had some scripts running on a windows runner using py <script.py> in an action. The runner updated, everything broke, and we noticed that even though setup-python is installing everything correctly - if another version is there (in this case a newer version) running anything with py can use the other version instead of the one that was just installed by setup-python.
Are you willing to submit a PR?
Happy to! I just didn't want to to put time into it if the feature is not a good idea / I'm missing something. Setting the PY_PYTHON env var in the actions worked for my specific case, though I'm wondering if to do it in general it should set any other py launcher related variables to match the newly installed python too.
The text was updated successfully, but these errors were encountered:
Description:
The
update-environment
flag updates seems to update a bunch of env variables to point at the newly installed version (cypthon example: https://github.com/actions/setup-python/blob/main/src/find-python.ts#L111).Could it also add the
PY_PYTHON=<version>
on Windows wheneverupdate-environment
is true? This will make the default version for the Windowspy
launcher match the one requested - even if the runner has another version already installed.Justification:
In short: make sure that
py <script.py>
runs on the version of python that you just installed withsetup-python
.I bumped into this because we had some scripts running on a windows runner using
py <script.py>
in an action. The runner updated, everything broke, and we noticed that even thoughsetup-python
is installing everything correctly - if another version is there (in this case a newer version) running anything withpy
can use the other version instead of the one that was just installed bysetup-python
.Are you willing to submit a PR?
Happy to! I just didn't want to to put time into it if the feature is not a good idea / I'm missing something. Setting the
PY_PYTHON
env var in the actions worked for my specific case, though I'm wondering if to do it in general it should set any otherpy
launcher related variables to match the newly installed python too.The text was updated successfully, but these errors were encountered: