PyLong_FromString() docs should point to C API functions rather than to int.to_bytes()/from_bytes()

[skirpichev]

Patch:

diff --git a/Doc/c-api/long.rst b/Doc/c-api/long.rst
index 42162914c0..a43a46a55a 100644
--- a/Doc/c-api/long.rst
+++ b/Doc/c-api/long.rst
@@ -94,9 +94,9 @@ distinguished from a number.  Use :c:func:`PyErr_Occurred` to disambiguate.
    ignored.  If there are no digits or *str* is not NULL-terminated following the
    digits and trailing whitespace, :exc:`ValueError` will be raised.
 
-   .. seealso:: Python methods :meth:`int.to_bytes` and :meth:`int.from_bytes`
-      to convert a :c:type:`PyLongObject` to/from an array of bytes in base
-      ``256``. You can call those from C using :c:func:`PyObject_CallMethod`.
+   .. seealso:: :c:func:`PyLong_AsNativeBytes()` and
+      :c:func:`PyLong_FromNativeBytes()` functions could be used to convert
+      a :c:type:`PyLongObject` to/from an array of bytes in base ``256``.
 
 
 .. c:function:: PyObject* PyLong_FromUnicodeObject(PyObject *u, int base)

Linked PRs

• gh-121477: mention new PyLong_*Bytes() functions in PyLong_FromString() #121478

[skirpichev]

@kumaraditya303, probably this should be backported to 3.13?