Use METH_NOARGS when no arguments are required #5488
Merged
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.
This PR first replaces '1' with METH_VARARGS in various locations, improving clarity. Changing code like this -
Pillow/src/_imaging.c
Lines 3421 to 3425 in d393cfb
to match how it is specified elsewhere in Pillow -
Pillow/src/_imagingft.c
Lines 1228 to 1230 in d393cfb
Then, this PR resolves #5487. The issue identifies 7 functions where we can use METH_NOARGS when no arguments are being used, rather than always using METH_VARARGS. This update is similar to #4441