Why was the JVM standalone distribution deprecated? #915
-
|
This may be a dumb question, but I've had trouble finding definitive answers online. I would appreciate it if someone were to explain why this distribution is no longer supported. It is my understanding that the only supported ways to run python now is on the native standalone distribution, or wrap it in a java project and use the maven/gradle plugin. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The JVM standalones always bundled a JDK, which meant we, the GraalPy team, essentially released a JDK. GraalPy supports more than one JDK vendor and version. We opted to no longer release a separate JVM standalone for now. At a later date, we may release JVM standalones again that consume whichever JDK is found via JAVA_HOME. For now, we offer a JBang! recipe ( |
Beta Was this translation helpful? Give feedback.
The JVM standalones always bundled a JDK, which meant we, the GraalPy team, essentially released a JDK.
GraalPy supports more than one JDK vendor and version. We opted to no longer release a separate JVM standalone for now. At a later date, we may release JVM standalones again that consume whichever JDK is found via JAVA_HOME. For now, we offer a JBang! recipe (
jbang graalpy@oracle/graalpython -c 'import sys; print(sys.implementation.name)') with which users can run the normal GraalPy launcher on whichever JDK they choose (with the caveat that some JDKs may offer reduced functionality)