-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[ty] Fix incorrect diagnostic when calling __setitem__
#19645
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
[ty] Fix incorrect diagnostic when calling __setitem__
#19645
Conversation
__setattr__
__setattr__
__setattr__
with no __getattr__
__setattr__
with no __getattr__
__setattr__
Diagnostic diff on typing conformance testsNo changes detected when running ty on typing conformance tests ✅ |
__setattr__
__setitem__
|
ah thanks |
I'm not sure how to check the conformance tests |
You can check out the https://github.com/python/typing repository and see the relevant files in its |
I don't immediately understand how this diff is related to your PR. This looks strange? |
Yeah looks very strange |
/cc @dhruvmanila Looks like maybe the merge base was computed incorrectly for the typing conformance check here? Edit: check previous version of the PR comment. |
they've gone away now at least |
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.
Thank you very much!
Summary
Resolves astral-sh/ty#862 by not emitting a diagnostic.
Test Plan
Add test to show we don't emit the diagnostic