-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
loop over python versions in github actions #9376
Comments
👋 I believe you can use UV_PYTHON instead |
Seems to be working:
|
I'd be happy to review a pull request adding documentation if needed. There's a bit at http://docs.astral.sh/uv/guides/integration/github/#setting-up-python but this sounds different. |
Although #9376 (comment) seems to be working, I'm still not clear if that's considered a recommendable/canonical approach. From the docs you linked ^^, there is also this option
but it's not obvious to me whether the python version here specifically overrides the python version that would be used by subsequent |
Yeah |
<!-- Thank you for contributing to uv! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? - Does this pull request include references to any relevant issues? --> ## Summary Existing documentation on how to apply a matrix strategy over the python version in a github workflow is incomplete and possibly misleading. This PR deletes the existing section and creates a new one to reflect current best practice. See #9376. ## Test Plan N/A, only docs. --------- Co-authored-by: Zanie Blue <contact@zanie.dev>
Here is what I did and it seems to work. But is that really the recommended way? It feels a bit hacky to overwrite
.python-version
. FWIW I'd appreciate any other feedback on that workflow config. I'm trying to set up uv with a few repos and would like to get my setup right.The text was updated successfully, but these errors were encountered: