shaunagm
commented
2 months ago Hi @bmos! Thanks for this PR. It looks like it decreases the Mac runs from about 3m each to 1m. I do wonder whether adding Python 3.11 and 3.12 to the matrix, which we plan to do soon, might cause usage issues again. I don't actually have much visibility into how close we are to the limit for the free tier, so I'll look into that. In the meantime, @bmos are you in our Slack? We'd love for you to join the community there. :)
bmos
What
uv is "an extremely fast Python package installer and resolver, written in Rust."
Why
Your macOS testing is significantly limited by only testing with python 3.8. Based on the comments in your actions, it seems like this is because macOS actions are much more expensive (and unfortunately that workflow takes even longer to run on macOS than it does on Windows). If the macOS workflow was able to execute faster, you could run more of them without incurring as much additional usage or just save your usage generally.
Your current workflow step of installing dependencies results in a notice:
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime.Both of these concerns can be addressed by using uv. Using the included linting workflow takes far less time per job compared to the workflow you're using now.
Why Not
uv is very new and relatively unknown compared to pip and does have some behavior differences from pip (such as how it does not default to installing yanked versions -- which could be a positive but is a noteworthy difference).
uv doesn't support python 3.7, which PyPI says parsons does (although parsons tests don't pass under 3.7)