Spicycrab: a Python-to-Rust transpiler demonstrated at Python Language Summit 2026

# What Spicycrab is

# How the demo worked

Kushal demonstrated a simple command-line transpile: crabpy transpile greet.py -o greet. That produced Rust source at greet/src/main.rs, which can then be run with cargo run. The demo also included an async web server case using actix-web. Kushal used generated Python stubs that mirror the actix-web API, wrote Python code with async functions and type annotations, transpiled that to idiomatic Rust, installed dependencies via Cargo, and compiled a binary that served HTTP responses.

# Who this is for

Kushal framed Spicycrab for teams constrained by a single virtual machine or limited resources where horizontal scaling isn't an option. Historically, such teams resorted to writing C extensions for hot paths, which brought complexity, crashes, and security concerns. Rust removes many of those safety concerns, but Rust's syntax can be a barrier. Spicycrab is aimed at developers who want the performance and safety improvements Rust offers without leaving Python.

• Spicycrab works by providing generated stubs for Rust libraries so Python code written to those stubs can be transpiled into equivalent Rust code that uses the real Rust libraries (actix-web in the demo).

# Comparison to other approaches

# Maintenance and cost considerations

# What to watch next

Spicycrab demonstrates a path for Python-first teams to leverage Rust performance while staying in Python's syntax for development. The demo highlights practical barriers—dependency compilation and long-term maintenance—that teams should weigh when considering this approach.