Use Python 3.12 for fuzz-parser in CI
#14159
Merged
Conversation
This file contains 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
MichaReiser
approved these changes
Nov 7, 2024
|
Python 3.13 breaks |
AlexWaygood
changed the title
fuzz-parser in CIfuzz-parser in CI
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Looks like merging #14156 broke CI on the
mainbranch. I thought I was safe to enable automerge as I'd done extensive testing locally -- more fool me!It looks like the problem is something to do with f-strings, so I'm guessing PEP-701 is to blame. Let's see if upgrading our Python versions in CI to 3.13 (which is what I used for local testing) fixes things.