[FR] Expose an `interpreter-path` output containing the chosen Python executable path

[webknjaz]

Description:

$sbj

Justification:

In a cross-platform matrix, there's often a need to be more specific about what you invoke. Plus the command for pointing at a specific interpreter may differ. For example, I recently discovered that invoking python3.10 which works great under *NIX fails on Windows with D:\a\_temp\7b307349-0858-40ae-97bf-a41c70e6d07c.sh: line 1: python3.10: command not found. And that is right after calling setup-python to switch to 3.10.

It would be so much easier and precise to just have ${{ steps.use-py310.outputs.interpreter-path }} used in place of that.

Are you willing to submit a PR?

Not sure, I've got a lot on my plate now so probably not. But feel free to tag me for code review.

[dhvcc]

May be you have an example of a workflow that triggers error on windows? May be there's a problem with installation steps

[mcous]

I just ran into this same issue (*nix has a python3.10 in the path, Windows does not), and went looking for the same solution - an output from the action specifying the path to the selected python.

It looks like there is an undocumented environment variable pythonLocation that may serve this same purpose

[dhvcc]

I just ran into this same issue (*nix has a python3.10 in the path, Windows does not), and went looking for the same solution - an output from the action specifying the path to the selected python.

It looks like there is an undocumented environment variable pythonLocation that may serve this same purpose

So, may be there is a workflow file so this behavior can be reproduced?