Don't install (nor run) mypy on PyPy (librt build failures)#187
Open
Avasam wants to merge 1 commit intojaraco:mainfrom
Open
Don't install (nor run) mypy on PyPy (librt build failures)#187Avasam wants to merge 1 commit intojaraco:mainfrom
Avasam wants to merge 1 commit intojaraco:mainfrom
Conversation
2 tasks
This was referenced Dec 20, 2025
This was referenced Jan 23, 2026
This was referenced Feb 8, 2026
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.
The latest reason is that librt, a new mypy dependency used for their new cache, doesn't build on PyPy.
But it's not the first time mypy can't be run on PyPy and it's not like running static type checking on PyPy actually brings anything other than wasting time. So I used a more generalized explanation so we're not tempted to remove the install exclusion.