python from msys64 directory gets invoked on windows

[prabhu]

My workflow has setup-python step followed by setup-ruby. Noticed that the python from msys64 directory is getting invoked, due to it appearing before the Python directory in the PATH.

C:/hostedtoolcache/windows/Ruby/3.4.5/x64/msys64/ucrt64/bin/python.exe: No module named pip

I think this line is responsible for this feature/bug.

setup-ruby/windows.js

Line 75 in 30011b6

path.unshift(`${msys2}\\mingw64\\bin`, `${msys2}\\usr\\bin`)

PATH variable in GitHub actions.

/c/hostedtoolcache/windows/cs/2.1.17/x64:/c/Users/runneradmin/cs/bin:/c/hostedtoolcache/windows/sbt/1.11.2/sbt/bin:/c/hostedtoolcache/windows/Java_Temurin-Hotspot_jdk/21.0.8-9.0/x64/bin:/c/hostedtoolcache/windows/Ruby/3.4.5/x64/bin:/c/hostedtoolcache/windows/Ruby/3.4.5/x64/msys64/ucrt64/bin:/c/hostedtoolcache/windows/Ruby/3.4.5/x64/msys64/usr/bin:/c/Users/runneradmin/AppData/Roaming/Python/Python312/Scripts:/c/hostedtoolcache/windows/Python/3.12.10/x64/Scripts:/c/hostedtoolcache/windows/Python/3.12.10/x64:

Would it be possible to make this configurable?

[MSP-Greg]

My workflow has setup-python step followed by setup-ruby.

If you reverse the steps, does it work? The MSYS2 path entries are needed for compiling extension gems. I don't believe python is directly being installed, it must be a build dependency of one of the packages, not sure which.

[prabhu]

Yes, it works after reversing the steps, which is good enough for now, although an option to disable this behaviour will be nice. Thank you for the prompt response!

[eregon]

There is windows-toolchain: none:

setup-ruby/action.yml

Lines 39 to 46 in 2a7b300

	windows-toolchain:
	description: |
	This input allows to override the default toolchain setup on Windows.
	The default setting ('default') installs a toolchain based on the selected Ruby.
	Specifically, it installs MSYS2 if not already there and installs mingw/ucrt/mswin build tools and packages.
	It also sets environment variables using 'ridk' or 'vcvars64.bat' based on the selected Ruby.
	At present, the only other setting than 'default' is 'none', which only adds Ruby to PATH.
	No build tools or packages are installed, nor are any ENV setting changed to activate them.

but then of course you won't be able to install Ruby C extensions.