Closed JMadgwick closed 5 months ago
Thank you for the report. It indeed looks like a release engineering mistake. I'll have a look
This is now fixed in master: https://github.com/oracle/graal/commit/7f29f8bd69ebeb74f4ba2ce0a7096388bf757dfa
I'll try to add a comment here when there will be a release that includes these changes.
Fixed in 23.1.2 release.
Steps to reproduce:
graalpy-jvm-23.1.0-linux-amd64.tar.gz
from releases. This is supposed to be the JVM configuration of Oracle GraalVM.graalpy
and run example "The Java Host Interop API" from the docs:Result:
Repeating the above but instead using the
graalpy-community-jvm-23.1.0-linux-amd64.tar.gz
release works as expected.The prompt appears too quickly for a JVM to be starting and running
./bin/graalpy --version
with the broken version returnsGraalPy 3.10.8 (Oracle GraalVM Native 23.1.0)
which makes me think that maybe this is a packaging error with the release?Also, when running
graalpy --help
the optionis only seen with the community edition. This should be in PythonOptions.java but I couldn't see it there. This is probably irrelevant as the option looks to be deprecated now there's intended to be two separate releases. In any case, when using this option on the binary in
graalpy-jvm-23.1.0-linux-amd64.tar.gz
the response isERROR: '--jvm' is only supported when this launcher is part of a GraalVM
.