10000 bpo-37590: Remove redundant docs of PyEval_EvalFrameEx by shihai1991 · Pull Request #14765 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content

bpo-37590: Remove redundant docs of PyEval_EvalFrameEx #14765

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 14, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions Doc/c-api/veryhigh.rst
Original file line number Diff line number Diff line change
Expand Up @@ -335,12 +335,12 @@ the same library that the Python runtime is using.

.. c:function:: PyObject* PyEval_EvalFrameEx(PyFrameObject *f, int throwflag)

This is the main, unvarnished function of Python interpretation. It is
literally 2000 lines long. The code object associated with the execution
frame *f* is executed, interpreting bytecode and executing calls as needed.
The additional *throwflag* parameter can mostly be ignored - if true, then
it causes an exception to immediately be thrown; this is used for the
:meth:`~generator.throw` methods of generator objects.
This is the main, unvarnished function of Python interpretation. The code
object associated with the execution frame *f* is executed, interpreting
bytecode and executing calls as needed. The additional *throwflag*
parameter can mostly be ignored - if true, then it causes an exception
to immediately be thrown; this is used for the :meth:`~generator.throw`
methods of generator objects.

.. versionchanged:: 3.4
This function now includes a debug assertion to help ensure that it
Expand Down
0