[ty] Don't promote module-literal types#23786
Merged
AlexWaygood merged 2 commits intomainfrom Mar 7, 2026
Merged
Conversation
Typing conformance resultsNo changes detected ✅Current numbersThe percentage of diagnostics emitted that were expected errors held steady at 87.10%. The percentage of expected errors that received a diagnostic held steady at 77.81%. |
Memory usage reportSummary
Significant changesClick to expand detailed breakdownsphinx
|
|
|
| Lint rule | Added | Removed | Changed |
|---|---|---|---|
invalid-argument-type |
12 | 0 | 3 |
unresolved-attribute |
0 | 0 | 4 |
invalid-assignment |
0 | 1 | 2 |
| Total | 12 | 1 | 9 |
Member
Author
|
The new ecosystem diagnostics on pycryptodome seem like a pretty clear improvement to me -- I've added an mdtest that's a minimized version of them and fails on |
charliermarsh
approved these changes
Mar 7, 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
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
The motivation for doing this was always pretty weak:
types.ModuleTypeis an extremely broad/vague type that isn't very useful to work with. You almost always do not want a specific module inferred as being atypes.ModuleTypeinstance unless you've explicitly annotated it as such.It also seems completely untested: no tests fail from this change.
Test plan
I added an mdtest that fails on
main.