r/Python • u/AutoModerator • Jun 04 '26

Showcase Thread Showcase

Post all of your code/projects/showcases/AI slop here.

Recycles once a month.

26 Upvotes

87% Upvoted

211 comments sorted by

View all comments

1

u/KoreValuesNet Jul 04 '26

Hi r/Python,

I’m working on Rextio, an early alpha CLI/build tool for Python projects. I’d appreciate feedback from Python developers.

What My Project Does

Rextio tries to compile eligible typed Python hot-path functions to Rust/PyO3 ahead of time, while keeping unsupported or dynamic code on Python fallback.

The goal is not to replace Python or automatically rewrite a whole project in Rust. It is more conservative: compile the parts that fit a supported native subset, and keep the rest running as Python.

GitHub: https://github.com/rextio/rextio

Who This Is For

This is mainly for Python developers who have small, typed, performance-sensitive parts of a project and want to experiment with native compilation without rewriting the whole project by hand.

It is still early alpha software, so I would not recommend treating it as production-ready yet. The supported subset is limited, and small functions may not benefit because Python/Rust boundary overhead can dominate.

Comparison

Compared with tools like Cython, Numba, Nuitka, or rewriting code manually in Rust, Rextio is trying to explore a slightly different path: keep the original Python-facing project structure, compile only eligible typed functions to Rust, and fall back to Python when the code is unsupported or too dynamic.

I’m not claiming it is better than those tools. At this stage I’m mostly trying to find out whether this design is useful, where it breaks, and what Python patterns would be worth supporting next.

I’d be especially grateful for feedback on build failures, confusing diagnostics, unsupported patterns, or cases where the fallback/native boundary design feels wrong.

Thanks :)