{{ message }}
[2.7] bpo-28261: Prevent raising SystemError where PyArg_ParseTuple is used to parse non-args#3213
Merged
serhiy-storchaka merged 1 commit intoAug 26, 2017
Merged
Conversation
Contributor
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
5 participants
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.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.
this is a partial backport of #3119.
(the 3 bugs that cause a SystemError to be raised and are fixed in #3198 don't exist on 2.7. This is because on 2.7, the code of these bugs uses PyArg_Parse (which doesn't assume it received a tuple) instead of PyArg_ParseTuple.)
https://bugs.python.org/issue28261