bpo-29548: no longer use PyEval_Call* functions - #14683
Merged
methane merged 1 commit intoJul 11, 2019
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
zooba
approved these changes
Jul 11, 2019
Copy link
Copy Markdown
Member
|
LMK if you'd like me to merge, or if you want additional review from someone else. |
Sorry, something went wrong.
lisroach
pushed a commit
to lisroach/cpython
that referenced
this pull request
Sep 10, 2019
DinoV
pushed a commit
to DinoV/cpython
that referenced
this pull request
Jan 14, 2020
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
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.
The PyEval_Call* functions should not be used anymore. This fixes the last few places where they are called within CPython.
CC @methane
https://bugs.python.org/issue29548