-
-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to uv pip compile
#2958
Switch to uv pip compile
#2958
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2958 +/- ##
=======================================
Coverage 99.63% 99.63%
=======================================
Files 120 120
Lines 17830 17830
Branches 3204 3204
=======================================
Hits 17765 17765
Misses 46 46
Partials 19 19 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you update autodeps too?
test-requirements.txt
Outdated
# -r test-requirements.in | ||
# pytest | ||
exceptiongroup==1.2.0 | ||
# via pytest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change too seems wrong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's intended, as we specify --python-version=3.8
. If we generate separate test-requirements-pyXX.txt
files for each python version we test we'll only get exceptiongroup
in the ones that are <3.11
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I think that means we should have a requirements
directory wherein we generate txt files for all versions we test.
I don't have 3.8 on my system you see
This reverts commit 383729f. It did not work.
I think once this uses that flag, this is good for me |
So, added I think we just need to wait for a proper release with these changes to come out, but otherwise this pull request should be almost done! |
Heads up we plan to cut a release today. |
Ok so it looks like everything is working except for an issue that happens when importing cryptography on the 3.13 runner, with this error: I don't think this is caused by uv, probably an issue with cryptography. |
I'm surprised pulling in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since I already subscribed to this PR, here is my 2cents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to try out this new --universal
flag (I'm not sure when it was added? but seems useful)
... but that can be a followup. This is good as a drop in replacement.
Co-authored-by: T-256 <132141463+T-256@users.noreply.github.com>
Weird SSL issue on MacOS 3.12 runner:
Pretty sure it isn't related to this pull request's changes though, going to try to get CI to run again. Might be an instance of test flakiness. |
This pull request follows up on #2956 and is attempting to switch the continuous integration system to use astral.sh' new tool uv.
This particular pull request is a subset of #2957 and is in charge of only replacing
pip-compile
.Originally posted by @A5rocks in #2957 (comment)