Remove obsolete (flags) from CALL_FUNCTION_EX docs

Author: tangyuan0821

Doc/library/dis.rst

@@ -1607,19 +1607,30 @@ iterations of the loop.
    .. versionadded:: 3.13
 
 
-.. opcode:: CALL_FUNCTION_EX (flags)
-
-   Calls a callable object with variable set of positional and keyword
-   arguments.  If the lowest bit of *flags* is set, the top of the stack
-   contains a mapping object containing additional keyword arguments.
-   Before the callable is called, the mapping object and iterable object
-   are each "unpacked" and their contents passed in as keyword and
-   positional arguments respectively.
-   ``CALL_FUNCTION_EX`` pops all arguments and the callable object off the stack,
-   calls the callable object with those arguments, and pushes the return value
-   returned by the callable object.
-
-   .. versionadded:: 3.6
+.. opcode:: CALL_FUNCTION_EX
+
+    Calls a callable object with a variable set of positional and keyword
+    arguments collected at runtime. It expects (in ascending order):
+
+    * the callable object
+    * ``NULL`` (a marker used in the calling convention; may be elided in
+       optimized internal forms)
+    * a :class:`tuple` containing the positional arguments
+    * either ``NULL`` or a :class:`dict` containing the keyword arguments
+
+    The positional arguments tuple and the keyword arguments dict are each
+    "unpacked" and passed to the callable. ``CALL_FUNCTION_EX`` pops all these
+    items and pushes the callable's return value.
+
+    Earlier Python versions documented an integer *flags* operand indicating
+    the presence of a mapping object for keyword arguments; this no longer
+    applies. The opcode itself no longer has a separate operand or flag bits
+    for this purpose in Python 3.14 and later.
+
+    .. versionadded:: 3.6
+    .. versionchanged:: 3.14
+         The obsolete *flags* argument was removed from the documentation; the
+         opcode no longer uses an operand to signal presence of ``**kwargs``.
 
 
 .. opcode:: PUSH_NULL