gh-102468: Document PyCFunction_New* and PyCMethod_New

Doc/c-api/structures.rst

@@ -399,6 +399,27 @@ definition with the same method name.
    slot.  This is helpful because calls to PyCFunctions are optimized more
    than wrapper object calls.
 
+.. c:function:: PyObject * PyCFunction_New(PyMethodDef *ml, PyObject *self)
+
+   Turn *ml* into a Python :term:`callable` object.  The *self* parameter will be
+   passed as the *self* argument to the C function in ``ml->ml_meth`` when
+   invoked. *self* can be ``NULL``.
+
+.. c:function:: PyObject * PyCFunction_NewEx(PyMethodDef *ml, PyObject *self, PyObject *module)
+
+   Same as :c:func:`PyCFunction_New`, but also allows setting the function
+   object's ``__module__`` attribute from the given *module* argument.
+   *module* should be the name of the module the function is defined in,
+   or ``None`` if unavailable.
+
+   .. seealso: :attr:`function.__module__`
+
+.. c:function:: PyObject * PyCMethod_New(PyMethodDef *ml, PyObject *self, PyObject *module, PyTypeObject *cls)
+
+   Same as :c:func:`PyCFunction_NewEx`, but accept a *cls* parameter, which
+   will be passed as the *defining_class* argument to the C function.
+   Must be set if :c:macro:`METH_METHOD` is set on ``ml->ml_flags``.
+
 
 Accessing attributes of extension types
 ---------------------------------------

Doc/data/refcounts.dat

@@ -402,6 +402,21 @@ PyContextVar_Reset:int:::
 PyContextVar_Reset:PyObject*:var:0:
 PyContextVar_Reset:PyObject*:token:-1:
 
+PyCFunction_New:PyObject*::+1:
+PyCFunction_New:PyMethodDef*:ml::
+PyCFunction_New:PyObject*:self:+1:
+
+PyCFunction_NewEx:PyObject*::+1:
+PyCFunction_NewEx:PyMethodDef*:ml::
+PyCFunction_NewEx:PyObject*:self:+1:
+PyCFunction_NewEx:PyObject*:module:+1:
+
+PyCMethod_New:PyObject*::+1:
+PyCMethod_New:PyMethodDef*:ml::
+PyCMethod_New:PyObject*:self:+1:
+PyCMethod_New:PyObject*:module:+1:
+PyCMethod_New:PyObject*:cls:+1:
+
 PyDate_Check:int:::
 PyDate_Check:PyObject*:ob:0: