ci: remove Python 3.13 preinstall workaround from unittest workflow#891
Merged
Merged
Conversation
# Conflicts: # .github/workflows/unittests.yml
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
1 participant
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
Remove the Python 3.13-specific preinstall workaround from the unittest workflow.
Details
The workflow now relies on the normal package install step for Python 3.13 instead of preinstalling and .
is already declared as a normal dependency for Python 3.13+ in , and is already provided through the build-system requirements.
Why
This historical workaround was needed when build behavior depended on the caller environment. After the move to packaging, that is no longer expected, so the extra preinstall step should no longer be necessary.
ref: #890