Documentation
Guides, API references, and troubleshooting for the Pyvorin platform.
Pyvorin vs Codon
Codon compiles Python-syntax code to standalone native binaries; Pyvorin compiles the Python you already run, in-process, beside CPython. Where each fits.
Pyvorin vs CPython
Pyvorin runs your existing Python as native machine code beside CPython. Where that helps, where it does not, and the measured results from 71 workloads.
Pyvorin vs Cython
Cython asks you to maintain a second language for speed. Pyvorin compiles the Python you already have. The right choice depends on who owns the code.
Pyvorin vs Mojo
Mojo and Pyvorin both promise Python-like ergonomics with native performance, but they answer different questions. Goals, fit, and honest trade-offs.
Pyvorin vs Nuitka
Nuitka's deliverable is a binary you can hand to a customer. Pyvorin's deliverable is speed inside the Python environment you already run. Choose accordingly.
Pyvorin vs Numba
Both tools turn Python into machine code through LLVM. The deciding factor is what your slow code looks like — and this page shows how to find out.
Pyvorin vs PyPy
PyPy replaces CPython with a faster interpreter and asks for nothing. Pyvorin keeps your runtime and compiles the hot paths. Compatibility decides most battles.