[SymForce] Use uv for requirements #392
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This lets us to an actual full solve for each python version, instead of
the ad-hoc patching we've been doing, which is much more scalable,
especially as parts of the ecosystem start dropping py3.8 and we're
trying to maintain py3.8 through 3.13 and beyond (at least for now?).
Afaik pip-tools isn't capable of doing a solve for python versions other
than what's installed, and uv is nicer anyway. uv also has this new
lockfile
thing they're pushing for, but it's uv-specific so I'd rather not lock us or
users into that.
Last I tried this, uv didn't support solving for python versions other
than the running interpreter; now they do (except that dependencies that
don't have wheels need to get built with an actual Python interpreter).
I previously had a GitHub action to build requirements for all Python
versions; it was super fast (<1m) and kinda convenient, it'd just make a
PR. I think I like just having the requirements test do it now though,
now that it's possible to do that way.
Topic: sf-uv