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 13e00b544818faf90bc0ea054578d5cf11570db4..14ca2b409969cfa471333ad9d75c5b6c0ab390c9 100644 (file)
--- a/Doc/c-api/exceptions.rst
+++ b/Doc/c-api/exceptions.rst
@@ -317,7 +317,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.