Rextio
Rextio 0.1.8 is an alpha-stage local build tool for Python projects,
published to PyPI on 2026-07-27 with plugin API 1.7, tooling contract
3.0.0. It supersedes 0.1.7 (2026-07-27; plugin API 1.7, tooling
contract 2.28.0), which superseded 0.1.6 (2026-07-26; plugin API 1.6,
tooling contract 2.27.0, readiness policy 11). It retains the experimental host
source-AOT/executable and bounded strict artifact-contract Alpha from Release Train C,
bounded plugin comparison expressions, Device Provider API 1
selection/preflight/build wiring, and fail-closed static device-domain
lowering authorization from 0.1.6, and adds optional plugin function-scope
RAII guards (API 1.7), and replaces public artifact lifecycle identities with
semantic artifact-* names. Core alone does not claim CUDA framework support,
certified accelerator execution, general artifact authorization, or general
package AOT.
pip install rextio
It analyzes typed Python code, compiles eligible hot-path functions to Rust native modules, and keeps unsupported or unsafe code on the Python fallback path. The goal is to let Python projects adopt Rust acceleration selectively without rewriting the whole project.
Rextio can:
- discover native candidates automatically or through
@rextio.native - keep selected functions on fallback with
@rextio.exempt - generate Rust/PyO3 code for accepted functions
- generate Python wrappers that preserve normal import paths
- fall back to Python when native code is unavailable or disabled
- build hybrid artifacts, zipapp executables, Nuitka executables, standalone native Rust binaries, and optional Rust-importable crates
- select and version-pin the exact cargo, maturin, Nuitka, and CPython a
build uses (
[toolchain]inrextio.toml) - explicitly select and preflight one compatible Device Provider for a statically authorized accelerator-bearing plugin domain
Rextio is not a Python replacement and does not attempt full Python semantics or whole-project Rust migration. Native compilation is an optimization; Python fallback behavior remains the correctness baseline.
Project repository: https://github.com/rextio/rextio
Author: Steve Si-young Song rextio.co@gmail.com — X (Twitter): @RextioDev
Metadata
Release files for rextio 0.1.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rextio-0.1.8.tar.gz | 1.1 MB | Without provenance | Details for rextio-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rextio-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for rextio-0.1.8-py3-none-any.whl |
Total release size: 2.2 MB
Release files / rextio-0.1.8.tar.gz
| Download URL | rextio-0.1.8.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
231f2ebee969d3d79104e5d0a00d134bd39f0d9ff540b75acb0612de4bf36238
|
|
BLAKE2b-256 checksum How to use checksums |
04f98e4b9abe0f287050b90dc4af1ea4b2ca5c55e212e771fbb80a9793407836
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Release files / rextio-0.1.8-py3-none-any.whl
| Download URL | rextio-0.1.8-py3-none-any.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
087175de4afa8785da4ed5958641baa633df6115ca3d0ae2ea4f892efb05be5c
|
|
BLAKE2b-256 checksum How to use checksums |
77d1cc285cca46706b242592a735efcf09645d009bb9b8672b732a0cd521aabd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Security for rextio 0.1.8
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.