Revert: [pyflakes] Avoid false positives in @no_type_check contexts (F821, F722) (#14615)#14726
Merged
Merged
Conversation
charliermarsh
approved these changes
Dec 2, 2024
charliermarsh
left a comment
Member
There was a problem hiding this comment.
Thanks. The PR itself was solid but it was my mistake to take this approach.
AlexWaygood
approved these changes
Dec 2, 2024
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.
Summary
Reverts #14615 due to #14698
The fix-bug seems worse than avoiding the few false positives. That's why I think we should revert this change
for now to give us more time to work on proper
@no_type_checksupport.Fixes #14698