Post

Charlie Marsh
@crmarsh.com

Today, we're announcing our first hosted infrastructure product: pyx, a Python-native package registry. We think of pyx as an optimized backend for uv: it’s a package registry, but it also solves problems that go beyond the scope of a traditional "package registry".

37 reposts172 likes

Thomas A Caswell
@tacaswell.bsky.social

"...optimized artifacts and uv-native metadata APIs" Does this mean you are extending wheels or layering extra metadata on top? If a layer on top can it be updated after build time? Are you rebuilding packages? Have you split out system deps into their own packages?

Charlie Marsh
@crmarsh.com

With pyx, uv becomes even faster, more secure, and hardware-aware (PyTorch, CUDA, FlashAttention, etc. become first-class citizens). You can use pyx to host private packages (it's much faster than other private registries), or as a frontend to public sources like PyPI.

Charlie Marsh
@crmarsh.com

Much of the inspiration for pyx comes from the classes of problems we see in the uv issue tracker that we can't solve with a client alone -- but could solve with a server. For example...