More cleanup.

Author: ZeroIntensity

Doc/c-api/profiling.rst

@@ -5,7 +5,6 @@
 Profiling and Tracing
 =====================
 
-
 The Python interpreter provides some low-level support for attaching profiling
 and execution tracing facilities.  These are used for profiling, debugging, and
 coverage analysis tools.
@@ -123,6 +122,7 @@ Python-level trace functions in previous versions.
 
    The caller must have an :term:`attached thread state`.
 
+
 .. c:function:: void PyEval_SetProfileAllThreads(Py_tracefunc func, PyObject *obj)
 
    Like :c:func:`PyEval_SetProfile` but sets the profile function in all running threads
@@ -149,6 +149,7 @@ Python-level trace functions in previous versions.
 
    The caller must have an :term:`attached thread state`.
 
+
 .. c:function:: void PyEval_SetTraceAllThreads(Py_tracefunc func, PyObject *obj)
 
    Like :c:func:`PyEval_SetTrace` but sets the tracing function in all running threads
@@ -161,11 +162,13 @@ Python-level trace functions in previous versions.
 
 .. versionadded:: 3.12
 
+
 Reference tracing
 =================
 
 .. versionadded:: 3.13
 
+
 .. c:type:: int (*PyRefTracer)(PyObject *, int event, void* data)
 
    The type of the trace function registered using :c:func:`PyRefTracer_SetTracer`.
@@ -181,23 +184,27 @@ Reference tracing
 
 .. versionadded:: 3.13
 
+
 .. c:var:: int PyRefTracer_CREATE
 
    The value for the *event* parameter to :c:type:`PyRefTracer` functions when a Python
    object has been created.
 
+
 .. c:var:: int PyRefTracer_DESTROY
 
    The value for the *event* parameter to :c:type:`PyRefTracer` functions when a Python
    object has been destroyed.
 
+
 .. c:var:: int PyRefTracer_TRACKER_REMOVED
 
    The value for the *event* parameter to :c:type:`PyRefTracer` functions when the
    current tracer is about to be replaced by a new one.
 
    .. versionadded:: 3.14
 
+
 .. c:function:: int PyRefTracer_SetTracer(PyRefTracer tracer, void *data)
 
    Register a reference tracer function. The function will be called when a new
@@ -219,6 +226,7 @@ Reference tracing
 
 .. versionadded:: 3.13
 
+
 .. c:function:: PyRefTracer PyRefTracer_GetTracer(void** data)
 
    Get the registered reference tracer function and the value of the opaque data

Doc/c-api/subinterpreters.rst

@@ -246,6 +246,8 @@ function. You can create and destroy them using the following functions:
 A Per-Interpreter GIL
 ---------------------
 
+.. versionadded:: 3.12
+
 Using :c:func:`Py_NewInterpreterFromConfig` you can create
 a sub-interpreter that is completely isolated from other interpreters,
 including having its own GIL.  The most important benefit of this
@@ -279,8 +281,6 @@ any standard approach to this yet.  A future stdlib module would help
 mitigate the effort of preserving isolation and expose effective tools
 for communicating (and sharing) data between interpreters.
 
-.. versionadded:: 3.12
-
 
 Bugs and caveats
 ----------------
@@ -332,6 +332,7 @@ High-level APIs
       of a :ref:`per-interpreter GIL <per-interpreter-gil>`.
       See :c:func:`Py_NewInterpreterFromConfig`.
 
+
 .. c:function:: PyInterpreterState* PyInterpreterState_Get(void)
 
    Get the current interpreter.
@@ -380,6 +381,7 @@ High-level APIs
    .. versionchanged:: 3.11
       The *frame* parameter changed from ``PyFrameObject*`` to ``_PyInterpreterFrame*``.
 
+
 .. c:function:: _PyFrameEvalFunction _PyInterpreterState_GetEvalFrameFunc(PyInterpreterState *interp)
 
    Get the frame evaluation function.
@@ -388,6 +390,7 @@ High-level APIs
 
    .. versionadded:: 3.9
 
+
 .. c:function:: void _PyInterpreterState_SetEvalFrameFunc(PyInterpreterState *interp, _PyFrameEvalFunction eval_frame)
 
    Set the frame evaluation function.
@@ -430,6 +433,7 @@ All of the following functions must be called after :c:func:`Py_Initialize`.
    :term:`attached thread state` for the target interpreter. The interpreter
    state must have been reset with a previous call to :c:func:`PyInterpreterState_Clear`.
 
+
 .. _advanced-debugging:
 
 Advanced Debugger Support

Doc/c-api/threads.rst

@@ -710,7 +710,7 @@ pointer and a void pointer argument.
    .. versionchanged:: 3.7
       The type of the *id* parameter changed from :c:expr:`long` to
       :c:expr:`unsigned long`
-.
+
 
 .. _thread-local-storage:
 
@@ -768,7 +768,7 @@ CPython interpreter.  This API uses a new type :c:type:`Py_tss_t` instead of
 
 
 Dynamic Allocation
-~~~~~~~~~~~~~~~~~~
+------------------
 
 Dynamic allocation of the :c:type:`Py_tss_t`, required in extension modules
 built with :ref:`Py_LIMITED_API <stable>`, where static allocation of this type
@@ -795,7 +795,7 @@ is not possible due to its implementation being opaque at build time.
 
 
 Methods
-~~~~~~~
+-------
 
 The parameter *key* of these functions must not be ``NULL``.  Moreover, the
 behaviors of :c:func:`PyThread_tss_set` and :c:func:`PyThread_tss_get` are
@@ -843,8 +843,8 @@ undefined if the given :c:type:`Py_tss_t` has not been initialized by
 
 .. _thread-local-storage-api:
 
-Thread Local Storage (TLS) API
-------------------------------
+Legacy API
+----------
 
 .. deprecated:: 3.7
    This API is superseded by