TYP: setup pyrefly - #507
Open
neutrinoceros wants to merge 1 commit into
Open
Conversation
Owner
Author
|
pre-commit checks failures are unrelated (idefix recently gained a couple |
neutrinoceros
force-pushed
the
typ/pyrefly
branch
from
May 22, 2026 12:14
c722048 to
2799cb5
Compare
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.
a couple pyrefly bugs I uncovered while running it against inifix:
isinstancesupport (unions should be treated as runtime types) facebook/pyrefly#3408beyond these, pyrefly doesn't report anything here. Configuration can be merged now but CI integration will require these upstream defects to be addressed.