apollo-python
PyO3 bindings for the Apollo workspace.
Distribution
GitHub Releases tagged apollo-fft-v<version> build locked Linux, Windows,
and universal macOS wheels, install and import each artifact, attach the
validated wheel set and SHA-256 checksums to the release, and publish the same
wheels to apollo-fft on PyPI through OIDC Trusted Publishing. The tag
version must equal the apollo-python Cargo package version; Python metadata
reads that Cargo version rather than maintaining a second version field.
Architecture
src/
domain/ Python-facing domain boundary marker
application/ binding orchestration boundary marker
infrastructure/ host/runtime integration boundary marker
lib.rs PyO3 module, class, and function exports
apollo-python is an adapter crate. It owns Python type conversion,
contiguity validation, error translation into PyValueError, and PyO3 module
registration. The mathematical single sources of truth remain in the owning
Rust crates:
apollo-fftowns CPU FFT plans, precision profiles, full-spectrum 1D/2D/3D execution, and real-to-complex helpers.apollo-fftowns WGPU backend capability discovery surfaced throughavailable_backends()andbackend_capabilities().apollo-nufftowns exact and fast NUFFT execution.
The binding layer does not implement transform kernels. It validates Python
array layout, maps precision strings to Apollo PrecisionProfile values, and
delegates computation to the owning crate APIs.
Mathematical Contract
FFT bindings preserve Apollo's normalization convention: forward transforms are
unnormalized and inverse transforms divide by the transformed volume. The
rfft3 and irfft3 functions expose Apollo's full-spectrum real transform
contract rather than a half-spectrum NumPy compatibility surface.
NUFFT bindings preserve the owning crate's uniform-domain contracts. Positions, values, grid spacing, output shape, and kernel width are validated before delegation; invalid contracts are returned as Python value errors.
Precision Contract
Python callers select precision with:
high_accuracy:f64/complex128storage andf64compute.low_precision:f32/complex64storage andf32compute.mixed_precision:f32Python input converted tof16storage for Apollo's mixedf16/f32path where exposed by the owning FFT plan.
Storage/profile mismatches are rejected before transform execution. WGPU capability metadata reports the backend precision profiles that are actually available on the host.
Verification
This crate is verified through workspace checks and the PyO3 unit target:
cargo clippy --workspace --all-targets -- -D warningscargo test --workspace --all-targets
The workspace tests cover Python binding compilation, backend capability
metadata shape, full-spectrum rfft3/irfft3 value semantics, contiguity
rejection paths, and delegated CPU/WGPU/NUFFT API compatibility.
Metadata
Release files for apollo-fft 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| apollo_fft-0.2.0-cp38-abi3-win_amd64.whl | CPython 3.8 | abi3 | Windows x86-64 | Details for apollo_fft-0.2.0-cp38-abi3-win_amd64.whl |
| apollo_fft-0.2.0-cp38-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.8 | abi3 | Linux glibc 2.17+ x86-64 | Details for apollo_fft-0.2.0-cp38-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| apollo_fft-0.2.0-cp38-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl | CPython 3.8 | abi3 | macOS 11.0+ ARM64, macOS 10.12+ universal2 (ARM64, x86-64), macOS 10.12+ x86-64 | Details for apollo_fft-0.2.0-cp38-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl |
Total release size: 16.5 MB
Release files / apollo_fft-0.2.0-cp38-abi3-win_amd64.whl
| Download URL | apollo_fft-0.2.0-cp38-abi3-win_amd64.whl |
|---|---|
| Size | 3.8 MB |
| Tags | CPython 3.8 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
4eef82e6a1fb1f5e94be3c25a970b52e04cea7be069b91d5211e23935acef4f8
|
|
BLAKE2b-256 checksum How to use checksums |
2c6cc68e35f14a8180624d589af6dfa7f34df14fbefada6bef873315da92d7d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 22, 2026.
Transparency logRelease files / apollo_fft-0.2.0-cp38-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | apollo_fft-0.2.0-cp38-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.8 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
245d5f6ed5842f573da9ea8a8d68fcb4cf47d43e28693fe5cc488f7940776b0a
|
|
BLAKE2b-256 checksum How to use checksums |
422999d1ce658701e4b094293fb6c4fd56c8a62d5c0d1c844f1a3ea6274bba28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 22, 2026.
Transparency logRelease files / apollo_fft-0.2.0-cp38-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl
| Download URL | apollo_fft-0.2.0-cp38-abi3-macosx_10_12_x86_64.macosx_11_0_arm64.macosx_10_12_universal2.whl |
|---|---|
| Size | 8.2 MB |
| Tags | CPython 3.8 abi3 macOS 10.12+ universal2 (ARM64, x86-64) macOS 10.12+ x86-64 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6db8dec05067e3d1b55a109f5d715b891aced05494c58cdbe99d0f8f3ecdcac9
|
|
BLAKE2b-256 checksum How to use checksums |
491f8d8deed7696cf308b8c151142e182e4bcad61584ee7d7af2f8919f463b2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 22, 2026.
Transparency logSecurity for apollo-fft 0.2.0
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.
Full provenance
All 3 files in this release have been uploaded with provenance metadata.
Attestation for apollo_fft-0.2.0-cp38-abi3-win_amd64.whl
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 Jul 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.