I've encountered two separate (not currently provided by nixpkgs) python packages that are built with maturin in the last week - orjson and tokenizers - and I can only imagine both that there are more out there, and that more are coming. I have orjson packaged very jankily by building it as a Rust crate directly using naersk, then stripping off the env vars from the resulting derivation and throwing them unceremoniously into buildPythonPackage. That works, but not in a way that I'd even dream of submitting it to nixpkgs - now that I've encountered my second package built using maturin it really is beginning to feel like this is something that buildPythonPackage should "just" handle transparently, the way it does Python packages with C extensions built-in. Anyone have any thoughts?