- Notifications
You must be signed in to change notification settings - Fork3.8k
Fix some METH_NOARGS usage, use METH_O where possible#3366
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Starbuck5 left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
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.
This is quite an impressive roundup! I read through everything and ran the tests locally, it looks good to me.
Left a couple minor comments for you to decide what to do with.
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.
LGTM 👍
Tests all pass locally on my windows machine.
This PR is primarily intended for better code quality and better error reporting, but this also helps a (really tiny) bit with performance.
Some functions that were supposed to be
METH_NOARGSwereMETH_VARAGS(which means that you could pass any arbitrary arguments to these functions and python would not complain)I also tried to apply
METH_Oin some places where they make the code clearer