C API "Initialization" docs suggest to use PyFrameObject fields that are no longer public

[chgnrdv]

Since #90992 PyFrameObject is an opaque structure, but Profiling and Tracing section of Initialization, Finalization and Threads part of C API docs suggests to use its private fields to change tracing behavior:

cpython/Doc/c-api/init.rst

Lines 1661 to 1665 in ba8aa1f

	.. c:var:: int PyTrace_LINE
	The value passed as the *what* parameter to a :c:type:`Py_tracefunc` function
	(but not a profiling function) when a line-number event is being reported.
	It may be disabled for a frame by setting :attr:`f_trace_lines` to *0* on that frame.

cpython/Doc/c-api/init.rst

Lines 1692 to 1697 in ba8aa1f

	.. c:var:: int PyTrace_OPCODE
	The value for the *what* parameter to :c:type:`Py_tracefunc` functions (but not
	profiling functions) when a new opcode is about to be executed. This event is
	not emitted by default: it must be explicitly requested by setting
	:attr:`f_trace_opcodes` to *1* on the frame.

I guess it should instead mention PyObject_SetAttrString(frame, "f_trace_lines", Py_False) and PyObject_SetAttrString(frame, "f_trace_opcodes", Py_True) calls as a way to set values of needed fields.

Linked PRs

• gh-111774: Update Tracing C API documentation: suggest to use PyObject_SetAttrString to set frame object fields #111776

[serhiy-storchaka]

:attr:`~frame.f_trace_lines` refers not to the field of the C structure, but to the attribute of the Python object. So technically the documentation is correct (beside that it is better to use False/True instead of 0/1). What C API you use to set the value of the attribute (PyObject_SetAttr() or PyObject_SetAttrString()) is unrelated.