Bump pyright test dependency to 1.1.299 #9958
Merged
Conversation
This file contains 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
AlexWaygood
commented
Mar 27, 2023
AlexWaygood
changed the title
|
It looks to me as if the 1.1.300 errors are related to annotations like: foo: int = ...I wouldn't mind if we'd "fix" them. (Actually I'm a bit surprised we don't have a flake8-pyi check.) |
|
Ugh, that again, coming back to haunt us :/// Tbh, I think it may be a bug in pyright (though yes, we should obviously use the But anyway, too much to work through right now! I really just wanted to see whether the pyright bugs I'm seeing in the CI for #9957 can be reproduced with a more up-to-date version of pyright. |
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.
No description provided.