-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
stubtest: fix false negative with dunder methods, small changes #8886
Conversation
The Appveyor CI failure isn't real. Looks like we may have disabled the Appveyor project but we still try to trigger it. Out of curiosity, what are the noisy results from enabling this for other dunders? |
I wasn't too thorough, but there were a number of complaints about |
Seems to be a little more reliable
I can no longer repro any of the behaviour related to distutils.command. I found one case it can come up involving builtins, but overall I think this code is just simpler like this.
If the stub doesn't list dunder methods, we wouldn't check them earlier. There are a lot of false negatives due to this.
Also covers some of the MRO logic in verify_typeinfo
c2279e3
to
c44e00a
Compare
#8786 just got merged, so let's try CI again |
cc @JelleZijlstra not sure how to request review, but everything is green now |
If a stub was completely missing a dunder method, we wouldn't check it against the runtime. It's noisy to check all dunder methods, but checking init, new and call catches a lot of false negatives on typeshed without much noise.