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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update
AnyClassMethod
for change in python/typeshed#9771 #5505update
AnyClassMethod
for change in python/typeshed#9771 #5505Changes from 3 commits
822cbb9
58cec71
a49c07a
4318311
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest reverting the change to the mypy version (i.e., change it back to 0.971 in
requirements-linting.txt
) and making this change instead, which I think should result in the update to the definition used by pyright but not mypy.I think this should keep everything else behaving the same (so we don't need to worry about breaking existing mypy functionality), but please confirm that this change would work for you with pyright.
As far as I'm currently aware it's not our intention to support mypy v1.2.0 with pydantic v1, given the various breaking changes (it will be supported in pydantic v2 though), so I wouldn't worry about updating the requirements-linting.txt.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It didn't work on the pright side as provided but it did work with the condition swapped. It also worked locally with
mypy==0.971
.