Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
mwsealey opened this issue Jan 17, 2025 · 2 comments
Assignees

Comments

@mwsealey
Copy link

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
Copy link
Author

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

@timfel
Copy link
Member

timfel commented Jan 19, 2025

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

@timfel timfel self-assigned this Jan 19, 2025
graalvmbot pushed a commit that referenced this issue Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants