OpenEquivariance JAX Extension
The JAX extension module for OpenEquivariance.
XLA FFI provider
The libjcn_ffi_openequivariance.so Bazel target builds a Python-independent
FFI provider against the XLA and CUDA repositories selected by the caller's
Bazel configuration:
bazel build @openequivariance_src//openequivariance_extjax:libjcn_ffi_openequivariance.so
The handler implementation owns one ABI-versioned table with slots for every
XLA stage (instantiate, prepare, initialize, and execute) plus each
target's traits. The nanobind extension reads that table and publishes only
stages that have a handler. The shared library exports RegisterFFi(const XLA_FFI_Api*, const char*); a runtime loader obtains the API from its PJRT
plugin and calls this entry point. The provider uses
XLA_FFI_Handler_Register to register every target as a complete handler
bundle, passing every non-null stage and the traits from the table. JAX
registration uses the same table.
1 maintainer
Release files for openequivariance-extjax 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| openequivariance_extjax-0.7.0.tar.gz | 29.7 kB | Details |
Release files / openequivariance_extjax-0.7.0.tar.gz
| Download URL | openequivariance_extjax-0.7.0.tar.gz |
|---|---|
| Size | 29.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e20e849329525a59d84b2e1b8e6d5690f234666182e3344cfee3f74a8a58bb3c
|
|
BLAKE2b-256 checksum How to use checksums |
e0cab4f38862f1d6455edc88290a92907d490708d97df96e2140c87c37bbd243
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency log
