[GR-58469] Cut ties with Sulong managed.

PullRequest: graalpython/3503

Author: timfel

README.md

@@ -4,8 +4,8 @@
 [![](https://img.shields.io/badge/pyenv-graalpy-blue)](#start-replacing-cpython-with-graalpy) 
 </a> [![Join Slack][badge-slack]][slack] [![GraalVM on Twitter][badge-twitter]][twitter] [![License](https://img.shields.io/badge/license-UPL-green)](#license)
 
-GraalPy is a high-performance implementation of the [Python](https://www.python.org/) language for the JVM built on [GraalVM](https://www.graalvm.org/). 
-GraalPy is a Python 3.11 compliant runtime. 
+GraalPy is a high-performance implementation of the Python language for the JVM built on [GraalVM](https://www.graalvm.org/python). 
+GraalPy is a Python 3.11 compliant runtime.
 It has first-class support for embedding in Java and can turn Python applications into fast, standalone binaries.
 GraalPy is ready for production running pure Python code and has experimental support for many popular native extension modules.
 
@@ -24,7 +24,7 @@ GraalPy is ready for production running pure Python code and has experimental su
 * Support for native extension modules is considered experimental, but you can already install [packages](docs/user/Python-Runtime.md#installing-packages) like *NumPy*, *PyTorch*, or *Tensorflow*; run [Hugging Face](https://huggingface.co/) models like *Stable Diffusion* or *GPT*
 ![](docs/user/assets/mcd.svg#gh-light-mode-only)![](docs/user/assets/mcd-dark.svg#gh-dark-mode-only)<sup>
 We run the tests of the [most depended on PyPI packages](https://libraries.io/pypi) every day.
-For 96% of those packages a recent version can be installed on GraalPy and GraalPy passes about 50% of all tests of all packages combined.
+For 97% of those packages a recent version can be installed on GraalPy and GraalPy passes over 60% of all tests of all packages combined.
 We assume that CPython not passing 100% of all tests is due to problems in our infrastructure that may also affect GraalPy.
 Packages where CPython fails all tests are marked as "not tested" for both CPython and GraalPy.
 </sup>

bisect-benchmark.ini

@@ -3,7 +3,7 @@
 # Usage:
 # - Create a temporary branch based on the main branch (or the bad commit)
 # - Fill in this configuration file, preferably using the automated script
-#   graalpython-apptests/scripts/create-bisect-config
+#   graal-enterprise/graalpython-enterprise/scripts/create-bisect-config
 # - Commit and push the file
 # - The push command output should give you a link to create a PR. Open it, but
 #   don't create a PR. Instead, you should execute the job on your commit using

ci.jsonnet

@@ -1 +1 @@
-{ "overlay": "b8527c2fa08fc88554559a4a54c9294155c84c4f" }
+{ "overlay": "5f2c190a2db5461ac877a32df039c3584ae08148" }

docs/contributor/CONTRIBUTING.md

@@ -273,7 +273,7 @@ There are also different options for how the Python interpreter is run, passed v
  * `default` - run using the standard options
  * `default-multi` - run using a shared engine, which is the mode that is recommended to embedders that want to spawn multiple isolated Python contexts
  * `native` - same as `default`, its name is due to the fact that it runs C extensions using a mixture of LLVM bitcode interpreted and compiled via GraalVM and real native libraries
- * `sandboxed` - this name is historical - this configuration requires Oracle GraalVM and runs all C extensions purely as LLVM bitcode on the GraalVM, without any access to the native OS libraries, i.e., using the `--llvm.managed` option for GraalVM.
+ * `sandboxed` - this name is historical - this configuration runs some modules such as the posix and sha3 modules with Java code instead of with native access.
 
 ### Configuration of the underlying GraalVM runtime
 

docs/user/Embedding-Permissions.md

@@ -35,7 +35,6 @@ This approach is the most compatible with CPython and provides bare access to th
 By default, this implementation bypasses the Truffle abstraction layer, and therefore it is not sandboxed and does not support custom implementations of [Truffle FileSystem service-provider](https://www.graalvm.org/truffle/javadoc/org/graalvm/polyglot/io/FileSystem.html), and other Polyglot API providers related to system interfaces.
 
 The native backend is chosen by default when GraalPy is started via the `graalpy` or any other Python related launcher.
-The exceptions are Python related launchers with `-managed` suffix available only in Oracle GraalVM (for example, `graalpy-managed`), which by default use the `java` POSIX backend.
 
 #### Limitations of the Native Backend
 
@@ -49,7 +48,7 @@ Known limitations are:
 This backend uses the [Truffle abstraction layer](https://github.com/oracle/graal/blob/master/truffle/docs/README.md) and therefore supports custom Polyglot API providers related to system interfaces and sandboxing.
 Because this abstraction is POSIX agnostic, it does not expose all the necessary functionality. Some functionality is emulated, and some functionality is unsupported.
 
-The Java backend is the default when GraalPy is run via the `Context` API, that is, [embedded in Java applications](https://github.com/oracle/graal/blob/master/docs/reference-manual/embedding/embed-languages.md), or when it is launched using Python-related launchers with the `-managed` suffix (available only in Oracle GraalVM).
+The Java backend is the default when GraalPy is run via the `Context` API, that is, [embedded in Java applications](https://github.com/oracle/graal/blob/master/docs/reference-manual/embedding/embed-languages.md).
 
 #### Limitations of the Java Backend
 

docs/user/Python-Standalone-Applications.md

@@ -9,7 +9,8 @@ redirect_from: /reference-manual/python/standalone-binaries/
 # Python Standalone Applications
 
 GraalPy enables you to create a Python application or library as a native application or JAR file with no external dependencies.
-The [Truffle framework](https://github.com/oracle/graal/tree/master/truffle) on which GraalPy is built, combined with the [Sulong LLVM runtime](https://github.com/oracle/graal/tree/master/sulong) that GraalPy leverages for managed execution of Python's native extensions, completely virtualizes all filesystem accesses, including those to the standard library and installed packages.
+The [Truffle framework](https://github.com/oracle/graal/tree/master/truffle) on which GraalPy is built virtualizes all filesystem accesses, including those to the standard library and installed pure Python packages.
+Packages that include native code can still circumvent this, however!
 
 GraalPy includes a module named `standalone` to create a Python binary for Linux, macOS, and Windows. 
 The modules bundles all your application's resources into a single file.

docs/user/assets/mcd-dark.svg

@@ -47,14 +47,13 @@ if(WIN32)
 require_var(CAPI_INC_DIR)
 require_var(TRUFFLE_H_INC)
 require_var(TRUFFLE_NFI_H_INC)
-require_var(LLVM_MODE)
 require_var(GRAALPY_EXT)
 
 if(NOT DEFINED SRC_DIR)
     set(SRC_DIR "${CMAKE_SOURCE_DIR}")
 endif()
 
-set(TARGET_LIBPYTHON "python-${LLVM_MODE}")
+set(TARGET_LIBPYTHON "python-native")
 
 ######################################################################
 # common variables and compile/link options (for all build targets)
@@ -75,11 +74,7 @@ add_compile_definitions(
     GRAALVM_PYTHON_LLVM
 )
 
-if(${LLVM_MODE} STREQUAL "native")
-    add_compile_definitions(GRAALVM_PYTHON_LLVM_NATIVE)
-else()
-    add_compile_definitions(GRAALVM_PYTHON_LLVM_MANAGED)
-endif()
+add_compile_definitions(GRAALVM_PYTHON_LLVM_NATIVE)
 
 
 if(WIN32)

docs/user/assets/mcd.svg

@@ -48,20 +48,8 @@
 #define HANDLE_BASE 0x8000000000000000ULL
 #define IMMORTAL_REFCNT (INT64_MAX >> 1)
 
-#ifdef GRAALVM_PYTHON_LLVM_MANAGED
-/*
- * We can't include sulong headers here, they include stdbool.h and CPython has a test that
- * Python.h won't pull in stdbool.h
- */
-PyAPI_FUNC(int) points_to_py_handle_space(void* ptr);
-#define stub_to_pointer(STUB_PTR) (STUB_PTR)
-#define pointer_to_stub(O) (O)
-#else /* GRAALVM_PYTHON_LLVM_MANAGED */
-
 #define points_to_py_handle_space(PTR) ((((uintptr_t) (PTR)) & HANDLE_BASE) != 0)
 #define stub_to_pointer(STUB_PTR) (((uintptr_t) (STUB_PTR)) | HANDLE_BASE)
 #define pointer_to_stub(PTR) ((PyObject *)(((uintptr_t) (PTR)) & ~HANDLE_BASE))
 
-#endif /* GRAALVM_PYTHON_LLVM_MANAGED */
-
 #endif /* SRC_HANDLES_H_ */