Manage python versions#267
Merged
Merged
Conversation
Currently developer experience sucks since the project may or may not run on a specific python version for various reasons. We don't really want to start extensively testing on multiple versions but we can start using a standard version Use uv in the Makefile to make sure both virtual envs use a specified Python version. This is done with a "bootstrap" virtual env that runs on whatever python happens to be available. Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
24c041e to
f688c04
Compare
jku
commented
Oct 30, 2025
jku
commented
Oct 31, 2025
di
approved these changes
Oct 31, 2025
Member
Author
|
#269 is making some sort of dependency change very much required so let's try this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 is an attempt to solve #266. I'd like to standardize the Python version and still keep the developer experience sensible. Specific problem situations I am trying to handle:
I came up with this:
@woodruffw what do you think, is this bonkers (also as potential solution for gh-action-sigstore-python)?
Also CC @aaronlew02, @loosebazooka RE discussion on #266