https://bugzilla.redhat.com/show_bug.cgi?id=2313784
--- Comment #5 from Fabio Valentini decathorpe@gmail.com --- Regarding 1)
%generate_buildrequires %pyproject_buildrequires %cargo_generate_buildrequires
In this case, the Python dependency generator runs first because ... it is first in the script. 🥇 If switching these two around isn't enough, then we'll need to figure out something else. I seem to remember having seen this issue in some place before, but I can't remember details right now.
Regerding 2)
I think replacing this line:
jiter = { path = "../jiter", features = ["python", "num-bigint"] }
with this one:
jiter = { version = "0.5.0", features = ["python", "num-bigint"] }
should work to use the jiter sources from the rust-jiter package instead of the ones bundled here.
Keep in mind that this will likely tie the update cycle of this package with the one of rust-jiter, since they're published together from https://github.com/pydantic/jiter/, as far as I can tell.
If you want to keep things independent, building *without* adding a dependency on rust-jiter might make things more flexible. In this case, I would recommend taking the patches from rust-jiter to avoid the codspeed dependency.