Separate Pyright basic and stricter checks - #16280
Open
Mohith1612 wants to merge 1 commit into
Open
Conversation
Mohith1612
marked this pull request as ready for review
August 21, 2026 12:08
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.
Closes #16005.
The basic Pyright job now uses a dedicated config containing the paths excluded from stricter checks, while a structure check keeps both lists synchronized. This preserves existing Pyright coverage: each eligible stdlib and third-party stub is checked under either basic or stricter settings, with regression test cases continuing to use their dedicated config.
I pair programmed with Codex and have verified the code myself.