Fix doc: functions are not documented

Author: vstinner

Doc/deprecations/c-api-pending-removal-in-3.20.rst

@@ -1,8 +1,8 @@
 Pending removal in Python 3.20
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-* :c:func:`_PyObject_CallMethodId`, :c:func:`_PyObject_GetAttrId` and
-  :c:func:`_PyUnicode_FromId` are deprecated since 3.15 and will be removed in
+* :c:func:`!_PyObject_CallMethodId`, :c:func:`!_PyObject_GetAttrId` and
+  :c:func:`!_PyUnicode_FromId` are deprecated since 3.15 and will be removed in
   3.20. Instead, use :c:func:`PyUnicode_FromString()` and cache the result in
   the module state, then call :c:func:`PyObject_CallMethod` or
   :c:func:`PyObject_GetAttr`.

Doc/whatsnew/3.15.rst

@@ -1211,8 +1211,8 @@ Deprecated C APIs
   use the :c:type:`PyBytesWriter` API instead.
   (Contributed by Victor Stinner in :gh:`129813`.)
 
-* :c:func:`_PyObject_CallMethodId`, :c:func:`_PyObject_GetAttrId` and
-  :c:func:`_PyUnicode_FromId` are deprecated since 3.15 and will be removed in
+* :c:func:`!_PyObject_CallMethodId`, :c:func:`!_PyObject_GetAttrId` and
+  :c:func:`!_PyUnicode_FromId` are deprecated since 3.15 and will be removed in
   3.20. Instead, use :c:func:`PyUnicode_FromString()` and cache the result in
   the module state, then call :c:func:`PyObject_CallMethod` or
   :c:func:`PyObject_GetAttr`.

Misc/NEWS.d/next/C_API/2025-12-03-14-41-07.gh-issue-141049.VuAUe2.rst

@@ -1,5 +1,5 @@
-:c:func:`_PyObject_CallMethodId`, :c:func:`_PyObject_GetAttrId` and
-:c:func:`_PyUnicode_FromId` are deprecated since 3.15 and will be removed in
+:c:func:`!_PyObject_CallMethodId`, :c:func:`!_PyObject_GetAttrId` and
+:c:func:`!_PyUnicode_FromId` are deprecated since 3.15 and will be removed in
 3.20. Instead, use :c:func:`PyUnicode_FromString()` and cache the result in
 the module state, then call :c:func:`PyObject_CallMethod` or
 :c:func:`PyObject_GetAttr`. Patch by Victor Stinner.