[GR-76450] Move JBang catalog out of GraalPython

PullRequest: graalpython/4632

Author: timfel

CHANGELOG.md

@@ -5,7 +5,7 @@ language runtime. The main focus is on user-observable behavior of the engine.
 
 ## Version 25.1.0
 * The standalone artifacts now include the Python version name before the Graal version. The new artifacts now start with `graalpy<PYTHON_VERSION>-<GRAAL_VERSION>-<OPERATING_SYSTEM>-<ARCHITECTURE>`.
-* Standalone JVM artifacts are no longer released as separate distributions. For standalone deployments, use the GraalPy native artifacts. If you require Java interoperability, use a custom embedding.
+* Standalone JVM artifacts are no longer released as separate distributions. For standalone deployments, use the GraalPy native artifacts. If you require Java interoperability, use our jbang launcher (`jbang graalpy@oracle/graalpython -c "print('hello from GraalPy')"`) or a custom embedding.
 * Add `-X jit=0|1|2` presets to tune startup-heavy or throughput-oriented workloads, and make the GraalPy launcher default to the `jit=1` preset.
 * Treat foreign buffer objects as Python buffer-compatible binary objects, so APIs like `memoryview`, `bytes`, `bytearray`, `binascii.hexlify`, and `io.BytesIO` work naturally on them when embedding GraalPy in Java. This allows passing binary data between Python and Java's `ByteBuffer` and `ByteSequence` types with minimal (sometimes zero) copies.
 * Add support for [Truffle source options](https://www.graalvm.org/truffle/javadoc/com/oracle/truffle/api/source/Source.SourceBuilder.html#option(java.lang.String,java.lang.String)):

docs/site/Gemfile.lock

@@ -1,6 +1,6 @@
 GIT
   remote: https://github.com/graalvm/graal-languages-jekyll-theme.git
-  revision: 1e8d5b675768ea158684474ef7a32a6ed8ce9baf
+  revision: 6ae97469860513f340ee832c7b84be81c43d52ad
   branch: main
   specs:
     graal-languages-jekyll-theme (0.2.0)
@@ -43,10 +43,10 @@ GEM
       fiber-storage
     fiber-storage (1.0.1)
     forwardable-extended (2.6.0)
-    google-protobuf (4.34.1-arm64-darwin)
+    google-protobuf (4.35.0-arm64-darwin)
       bigdecimal
       rake (~> 13.3)
-    google-protobuf (4.34.1-x86_64-linux-gnu)
+    google-protobuf (4.35.0-x86_64-linux-gnu)
       bigdecimal
       rake (~> 13.3)
     hashery (2.1.2)
@@ -140,9 +140,9 @@ GEM
     rouge (4.7.0)
     ruby-rc4 (0.1.5)
     safe_yaml (1.0.5)
-    sass-embedded (1.99.0-arm64-darwin)
+    sass-embedded (1.100.0-arm64-darwin)
       google-protobuf (~> 4.31)
-    sass-embedded (1.99.0-x86_64-linux-gnu)
+    sass-embedded (1.100.0-x86_64-linux-gnu)
       google-protobuf (~> 4.31)
     siteleaf (2.3.0)
       httparty (>= 0.16.0)

docs/user/Python-on-JVM.md

@@ -8,9 +8,16 @@ While GraalPy offers similar capabilities to Jython, there are important differe
 
 This guide shows you how to migrate from Jython to GraalPy.
 
+For a lightweight command-line JVM launcher similar to the Jython launcher, use the JBang recipe from the GraalPy catalog:
+
+```bash
+jbang graalpy@oracle/graalpython -c "print('hello from GraalPy')"
+```
+
 ### Prerequisites
 
-- To migrate Jython scripts to GraalPy, you first need to create a GraalPy embedding. For more information, see [Embedding Python in Java](Embedding-Getting-Started.md).
+- To migrate plain Jython command-line scripts, you can create a custom embedding or run GraalPy with the JBang recipe.
+- To migrate applications that embed Jython, create a GraalPy embedding. For more information, see [Embedding Python in Java](Embedding-Getting-Started.md).
 - Make sure to migrate code from Python 2 (as supported by Jython) to Python 3 (the major version GraalPy is compatible with) following [the official guide from the Python community](https://docs.python.org/3/howto/pyporting.html)
 
 ## GraalPy Java Interoperability Overview

graalpython/com.oracle.graal.python.test/src/tests/conftest.toml

@@ -3,7 +3,6 @@ run_top_level_functions = true
 
 [[test_rules]]
 selector = [
-  "standalone/test_jbang_integration.py",
   "standalone/test_standalone.py"]
 per_test_timeout = 2400
 partial_splits_individual_tests = true

graalpython/graalpy-jbang/examples/hello.java

@@ -161,6 +161,16 @@ def create_if_needed(d):
                              'Python interpreter. Provide an explicit path or '
                              'check that your PATH environment variable is '
                              'correctly set.')
+        if not os.path.exists(executable):
+            raise ValueError(
+                "GraalPy cannot create or populate a virtual environment, because the currently "
+                "running executable is not a single binary file. Create and populate the venv "
+                f"using a native GraalPy standalone {__graalpython__.get_graalvm_version()} "
+                "instead. You can then use the venv with the currently running executable by "
+                "setting the option `python.Executable` either as a Context option (if this is "
+                "an embedding) or as the commandline flag "
+                "`--python.Executable=<venv>/bin/python`."
+            )
         dirname, exename = os.path.split(os.path.abspath(executable))
         context.executable = executable
         context.python_dir = dirname

graalpython/graalpy-jbang/templates/graalpy-template.java.qute

@@ -107,7 +107,7 @@ def get_boolean_env(name, default=False):
 RUNNING_ON_LATEST_JAVA = os.environ.get("LATEST_JAVA_HOME", os.environ.get("JAVA_HOME")) == mx.get_jdk().home
 
 
-# this environment variable is used by some of our maven projects and jbang integration to build against the unreleased master version during development
+# this environment variable is used by some of our maven projects to build against the unreleased master version during development
 os.environ["GRAALPY_VERSION"] = GRAAL_VERSION
 
 MAIN_BRANCH = 'master'