Windows executable name determination is flaky as it does not consider file extensions

[mwsealey]

X:\>%GRAALVM%\graalpy
ERROR: Cannot determine the executable name from path: 'X:\graalpy-jvm-25.0.0.ea.04-dev-windows-amd64\bin\graalpy'

vs.

X:\>%GRAALVM%\graalpy.exe
Jan 17, 2025 9:22:51 AM org.graalvm.shadowed.org.jline.utils.Log logr
WARNING: Unable to create a system terminal, creating a dumb terminal (enable debug logging for more information)
Python 3.11.7 (Thu Jan 16 11:23:53 CST 2025)
[Graal, Oracle GraalVM, Java 25 (amd64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>

[mwsealey]

I forgot to note that it works fine in a venv, just not from the bare commandline (hence flaky)

[timfel]

Thanks for the report. Indeed, when %GRAALVM% is an absolute path, we erroneously skip determination of the extension

[msimacek]

Should be fixed by the linked commit.