bpo-37441: Fix wrong PyErr_SetImportErrorSubclass signature in doc (GH-14453)

(cherry picked from commit aeecf380660ea459d85bb5f59d76bb54f757b5be)

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

diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst
index d3f6daa8347e413f7684975f3aba398a991bcf28..d8173935596bb85256a4415ed3e843a19d2937bc 100644 (file)
--- a/Doc/c-api/exceptions.rst
+++ b/Doc/c-api/exceptions.rst
@@ -320,7 +320,7 @@ an error value).
    :mod:`warnings` module and the :option:`-W` option in the command line
    documentation.  There is no C API for warning control.
 
-.. c:function:: PyObject* PyErr_SetImportErrorSubclass(PyObject *msg, PyObject *name, PyObject *path)
+.. c:function:: PyObject* PyErr_SetImportErrorSubclass(PyObject *exception, PyObject *msg, PyObject *name, PyObject *path)
 
    Much like :c:func:`PyErr_SetImportError` but this function allows for
    specifying a subclass of :exc:`ImportError` to raise.