[Django] Force python3 to point to python3.10. #11401
Merged
Conversation
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
|
apollo13 has previously contributed to projects/django. The previous PR was #11391 |
DavidKorczynski
approved these changes
Dec 23, 2023
Contributor
Author
|
@DavidKorczynski I need some help here :/ The builds still fail because the base-runner image has python3.8 which cannot parse syntax from python 3.10 https://oss-fuzz-build-logs.storage.googleapis.com/log-da714fe7-a150-4395-bb4c-fdcf486d775e.txt How can we work around that? Is there a way to have a custom runner for a project? |
Collaborator
|
I'll give it a try -- will ping here shortly |
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 seems to be required otherwise the coverage helper scripts will use python 3.8 leading to syntax errors.