-
Notifications
You must be signed in to change notification settings - Fork 206
Migrate from pyenv to uv #1995
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
Migrate from pyenv to uv #1995
Conversation
|
The non-required ci workflow Benchmark Hyper Threading / benchmark (pull_request) fails because main doesnt use uv yet |
|
Benchmark Results for unmodified programs 🚀
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1995 +/- ##
=======================================
Coverage 96.67% 96.67%
=======================================
Files 103 103
Lines 43568 43568
=======================================
Hits 42118 42118
Misses 1450 1450 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
71938e6 to
6d8c8fe
Compare
6d8c8fe to
b8ea96d
Compare
JulianGCalderon
left a comment
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 squashed the commits because we had a unsigned commit in the history, and I encountered conflicts while trying to rebase all commits.
This migrates the python workflow from
pyenvto the fast modern rust baseduv.The only takeaway is that the
pypyversions you can install fromuvdoesn't seem to work well with thebitarraydependency we have, as it fails to compile. Aspypywas only used inrun_benchmarks.sh, which was an outdated script that we no longer used, I also removed it.I also tried to update python to 3.13.2 but
cairo-rundoesnt work well, howevercairo-compiledoes work well. In the end I kept the old python version 3.9.