feat: install python with uv

[SMoraisAnsys]

As title says. Could be very usefull when one wants to use our actions in containers where python provided by actions/setup-python does not work directly.

The draft still needs to be updated to point to the main branch.

Associated to #1218

[SMoraisAnsys]

I'm switching this into PR to get feedback on it :D I was hoping to get some from #1218 but that wasn't the case :(

[RobPasMue]

I've go my doubts regarding this... why not reuse the "use-uv" input? If we use uv it should be a consistent usage IMO..

Adding optional inputs/flags is just going to introduce confusion

[SMoraisAnsys]

I've go my doubts regarding this... why not reuse the "use-uv" input? If we use uv it should be a consistent usage IMO..

Adding optional inputs/flags is just going to introduce confusion

I'm fine with it but that will change the previous behavior of our action. The main usage of uv was through the idea of providing uv to install packages. If the majority agreeds to using uv's python when using uv (which makes total sense) I'll do the changes ;)

@ansys/pyansys-core any strong opinion on one approach or the other ?

[moe-ad]

If we can rename use-uv to something that unambiguously reflects that it only installs packages (maybe use-uv-for-package-installation ?), I personally wouldn't mind adding another input for python installation.

If not, we probably shouldn't expose another input . We can instead document this as an additional behavior for the use-uv option in the migration guide to give the change more visibility. What do you think @SMoraisAnsys?

[SMoraisAnsys]

If we can rename use-uv to something that unambiguously reflects that it only installs packages (maybe use-uv-for-package-installation ?), I personally wouldn't mind adding another input for python installation.

If not, we probably shouldn't expose another input . We can instead document this as an additional behavior for the use-uv option in the migration guide to give the change more visibility. What do you think @SMoraisAnsys?

Fully moving to uv (python provider & package installation) might have side effects on certain workflows. Typically, I'm thinking about this issue astral-sh/python-build-standalone#596 but others might exist. We could probably bring that topic to one of our meeting. Leaving this PR as draft in the meantime.