I’ve been working on Pyra for the past few months and wanted to start sharing it in public.

Right now it’s focused on the core package/project management workflow: Python installs, init, add/remove, lockfiles, env sync, and running commands in the managed env.

The bigger thing I’m exploring is whether Python could eventually support a more cohesive toolchain story overall, more in the direction of Bun: not just packaging, but maybe over time testing, tasks, notebooks, and other common workflow tools feeling like one system instead of a bunch of separate pieces.

It’s still early, and I’m definitely not claiming it’s as mature as uv. I’m mostly sharing it now because I want honest feedback on whether the direction feels interesting or misguided.

Serious question: what does Pyra do differently from uv? Both are Rust-based, both use pyproject.toml, both focus on determinism, and uv already owns mindshare here with Astral's funding behind it.

A "why not uv" section in the README would probably be the single highest-leverage thing you could add - otherwise every second commenter in this thread will ask the same question and the actual differentiator (if there is one) gets lost in noise

Not clear what problem this is solving that uv and bun don’t already solve? This is like a solution looking for a problem.

If you enjoyed and learned from it I guess that’s what really matters.