uv2nix does not contain an override collection by design.
The uv2nix_hammer is a tool to automatically generate such overrides on demand.
These overrides are then collected in this repository so that downstream users can easily use uv2nix for the most common python packages.
Current state (2024-11-07): I have done a sweep through the 15.6k 'most important' python packages, prefering wheels. About 13.4k build, another 1000 have ended up on the exclusion list for various reasons, and the remaining ~650 are in limbo.
Poetry2nix might also benefit from these overrides, there's an example how to use them below. Note that poetry2nix builds python packages very differently from uv2nix, namely using nixpkgs python builders which have all kinds of drawbacks.
Example uv2nix flake.nix
Example poetry2nix flake.nix poetry2nix example
The first thing you might want to check is if there's a 'Downgrade*' rule in overrides/
One of your packages (or at least one dependency) has a limbo dependency - it's not declared correctly and uv didn't lock it. You can add it to the dependencies in you pyproject.toml.
Cython recently underwent a non-backwards compatible jump from 0.29 to 1.0. uv2nix_hammer_overrrides provides the former as cython_0, like nixpkgs does. It's not pretty, but it works for now.