Skip to content

Commit 64b2083

Browse files
committed
added changelog entries regarding python.embedding
1 parent 758af9a commit 64b2083

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

CHANGELOG.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,11 @@ language runtime. The main focus is on user-observable behavior of the engine.
2121
* Remove experimental `SetupLLVMLibraryPaths` option. It was used to pre-set library path for LLVM toolchain's libc++. The path can still be set manually.
2222
* Added `GRAALPY_VERSION` and `GRAALPY_VERSION_NUM` C macros
2323
* Added experimental `python.IsolateNativeModules` option to allow loading native extensions multiple times in different contexts. See [the documentation](https://github.com/oracle/graalpython/blob/master/docs/user/Native-Extensions.md) for more information.
24+
* GraalPy Embedding:
25+
* Introduced new types: KeywordArguments and PositionalArguments, in the GraalPy Embedding library (org.graalvm.python:python-embedding), to support directly passing [keyword and positional arguments](https://docs.python.org/3/glossary.html#term-argument) from Java to Python.
26+
* Deprecated the org.graalvm.python.embedding.util API package and added new equivalents to org.graalvm.python.embedding
27+
* Maven and Gradle plugins do not embed Python home into the generated virtual filesystem. Instead, the handling of language home for any Truffle language, including GraalPy, for the GraalVM Native Image build can be controlled by new Native Image options +H:IncludeLanguageResources and +H:CopyLanguageResources. By default, the whole Python home is embedded into the native executable. In the case of JVM deployment, the language home is embedded in the GraalPy artifacts at Mavencentral.
28+
* Removed deprecated methods in VirtualFileSystem
2429

2530
## Version 24.1.0
2631
* GraalPy is now considered stable for pure Python workloads. While many workloads involving native extension modules work, we continue to consider them experimental. You can use the command-line option `--python.WarnExperimentalFeatures` to enable warnings for such modules at runtime. In Java embeddings the warnings are enabled by default and you can suppress them by setting the context option 'python.WarnExperimentalFeatures' to 'false'.

0 commit comments

Comments
 (0)