aparnajyothi-y

Hello @kostrykin, Please confirm that the above mentioned workaround resolved the issue.

Hello @kostrykin, Please confirm that the above mentioned workaround resolved the issue or let us know in case any further clarifications needed.

Hello @kostrykin, Thank you for confirming that actions/setup-python is working successfully. We are proceeding to close this issue as it is not reproducible. Please feel free to reach out if...

Hello @ZeroIntensity, We are supporting python 3.8 and 3.9 versions for macos arm64 now. Please test your workflows. Closing this issue for now and let us know to reopen this...

Hello @edmorley, Thank you for creating this PR, we will review this PR and get back to you once we have some feedback on this.

Hello @marverix, Thank you for creating this issue and we will get back to you once we have some feedback :)

Hello @adamjstewart, Thank you for creating this issue once again. We are able to reproduce the issue in our local and investigated further. In the actions/setup-python GitHub action, the env.pythonLocation...

Hello @adamjstewart, We have investigated furthermore on this and found that there is difference in building installation packages before and after python 3.11 in actions/python-versions which setup-python uses to build...

Hello @adamjstewart, actions/setup-python defines env.pythonLocation and the functionality is to contains the absolute path to the folder where the requested version of Python or PyPy is installed.Python Building installation packages...

Hi @adamjstewart, The environment variable 'env.pythonLocation' is utilized by the 'actions/setup-python' action to indicate the installation location of the desired Python or PyPy version. This helps subsequent workflow steps to...