arraybridge
ArrayBridge provides explicit conversion and shared lifecycle utilities for NumPy, CuPy, PyTorch, TensorFlow, JAX, and pyclesperanto arrays.
Core dependencies are NumPy and metaclass-registry. Other frameworks are optional.
Quick start
import numpy as np
from arraybridge import convert_memory, detect_memory_type
value = np.arange(6).reshape(2, 3)
assert detect_memory_type(value) == "numpy"
copy = convert_memory(
value,
source_type="numpy",
target_type="numpy",
gpu_id=0,
)
convert_memory requires the declared source type, target type, and device id.
The source and target MemoryType declarations perform conversion directly.
The device id is required even for CPU conversions so call sites have one
stable signature. A GPU target must declare that identifier as available;
ArrayBridge does not silently place the value on the CPU.
Declarative decorators
from arraybridge import numpy
@numpy
def normalize(image):
return image / max(float(image.max()), 1.0)
The framework decorators attach input_memory_type, output_memory_type, and
execution_memory_type metadata, provide dtype/slice runtime parameters, and
add framework-specific stream/OOM handling where supported. They do not
convert inputs or outputs between frameworks and do not accept a gpu_id
argument. A host runtime must call convert_memory at the boundary it plans and
scope execution using the execution declaration.
Stack utilities
import numpy as np
from arraybridge import stack_slices, unstack_slices
slices = [np.zeros((8, 8)), np.ones((8, 8))]
stack = stack_slices(slices, memory_type="numpy", gpu_id=0)
restored = unstack_slices(stack, memory_type="numpy", gpu_id=0)
stack_slices requires non-empty 2D inputs. unstack_slices requires a 3D
array. Both validate shape and use explicit target memory/device declarations.
Installation
pip install arraybridge
pip install "arraybridge[torch]"
pip install "arraybridge[cupy]"
Documentation: https://arraybridge.readthedocs.io
Metadata
Release files for arraybridge 0.3.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| arraybridge-0.3.6.tar.gz | 101.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arraybridge-0.3.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 136.3 kB
Release files / arraybridge-0.3.6.tar.gz
| Download URL | arraybridge-0.3.6.tar.gz |
|---|---|
| Size | 101.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3b8a5821597a3341739657298ce94928cd1f4297a083fec3b28ceb406e09afb
|
|
BLAKE2b-256 checksum How to use checksums |
6a52450bbe1367dd1f4f9cac9ff685e72b9093e6efe391c6420280576bd6fede
|
| 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 Oct 2, 2026.
Transparency logRelease files / arraybridge-0.3.6-py3-none-any.whl
| Download URL | arraybridge-0.3.6-py3-none-any.whl |
|---|---|
| Size | 34.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7fa23f5dcf1925742592109b396fe17662fb56f15e1755a304a45c90e79a249
|
|
BLAKE2b-256 checksum How to use checksums |
c89d16d3f5b4b7dec3b0aa16d8df1b49cfd0d0e5e6a3c2b16fcb8f0fcbafe1c5
|
| 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 Oct 2, 2026.
Transparency log