TYP/CI: separate typing_requirements.txt#30872
Merged
charris merged 2 commits intonumpy:mainfrom Feb 24, 2026
Merged
Conversation
Member
|
This change is in #26255 as well, I can re-apply this |
Member
|
Might add an explanation in the new file so that it doesn't get merged back into test_requirements at some point. |
Member
|
Thanks Joren. |
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
3 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.
For (runtime) testing there is no need to install mypy and pyrefly, but because they were listed in
test_requirements.tst, they are installed in more workflows that needed.By splitting off the the type-checker requirements into a new
typing_requirements.txt, we can be more precise about this. The hope is that this will also resolve the armhf CI issues noted in #30863 (comment)