bpo-37590: Remove redundant docs of PyEval_EvalFrameEx (GH-14765)

(cherry picked from commit 40d2226a69aed6252023d365731bd4ed39dc1a4f)

Co-authored-by: Hai Shi <shihai1992@gmail.com>

diff --git a/Doc/c-api/veryhigh.rst b/Doc/c-api/veryhigh.rst
index e6704ddeca0906fed5f08397908acb332cf3e667..67dc11dfa9a537d9be3390bbc635171ad81bf435 100644 (file)
--- a/Doc/c-api/veryhigh.rst
+++ b/Doc/c-api/veryhigh.rst
@@ -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