gh-146615: Fix format specifiers in error messages for consistency and correctness - #146616
Closed
sunmy2019 wants to merge 2 commits into
Closed
gh-146615: Fix format specifiers in error messages for consistency and correctness#146616sunmy2019 wants to merge 2 commits into
sunmy2019 wants to merge 2 commits into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Copy link
Copy Markdown
Member
|
I would suggest:
Or 1 PR for real mistakes, 1 PR for the rest. |
Sorry, something went wrong.
Copy link
Copy Markdown
Member
Author
|
Split.
|
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewers
2 participants
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.
There are 2 kinds of errors.
There are ~8 real mistakes.
Comply with C99 for va_list: https://en.cppreference.com/w/c/variadic/va_arg.html
Most of the changes are %d <-> %ld for int and Py_ssize_t.