@@ -170,28 +170,56 @@ would typically correspond to a Python function.
170170 .. The table is here to make the docs searchable, and to allow automatic
171171 links to the identifiers.
172172
173- ================================================== =====================================
174- Macro Event
175- ================================================== =====================================
176- .. c:macro:: PY_MONITORING_EVENT_BRANCH_LEFT :monitoring-event:`BRANCH_LEFT`
177- .. c:macro:: PY_MONITORING_EVENT_BRANCH_RIGHT :monitoring-event:`BRANCH_RIGHT`
178- .. c:macro:: PY_MONITORING_EVENT_CALL :monitoring-event:`CALL`
179- .. c:macro:: PY_MONITORING_EVENT_C_RAISE :monitoring-event:`C_RAISE`
180- .. c:macro:: PY_MONITORING_EVENT_C_RETURN :monitoring-event:`C_RETURN`
181- .. c:macro:: PY_MONITORING_EVENT_EXCEPTION_HANDLED :monitoring-event:`EXCEPTION_HANDLED`
182- .. c:macro:: PY_MONITORING_EVENT_INSTRUCTION :monitoring-event:`INSTRUCTION`
183- .. c:macro:: PY_MONITORING_EVENT_JUMP :monitoring-event:`JUMP`
184- .. c:macro:: PY_MONITORING_EVENT_LINE :monitoring-event:`LINE`
185- .. c:macro:: PY_MONITORING_EVENT_PY_RESUME :monitoring-event:`PY_RESUME`
186- .. c:macro:: PY_MONITORING_EVENT_PY_RETURN :monitoring-event:`PY_RETURN`
187- .. c:macro:: PY_MONITORING_EVENT_PY_START :monitoring-event:`PY_START`
188- .. c:macro:: PY_MONITORING_EVENT_PY_THROW :monitoring-event:`PY_THROW`
189- .. c:macro:: PY_MONITORING_EVENT_PY_UNWIND :monitoring-event:`PY_UNWIND`
190- .. c:macro:: PY_MONITORING_EVENT_PY_YIELD :monitoring-event:`PY_YIELD`
191- .. c:macro:: PY_MONITORING_EVENT_RAISE :monitoring-event:`RAISE`
192- .. c:macro:: PY_MONITORING_EVENT_RERAISE :monitoring-event:`RERAISE`
193- .. c:macro:: PY_MONITORING_EVENT_STOP_ITERATION :monitoring-event:`STOP_ITERATION`
194- ================================================== =====================================
173+ .. list-table::
174+ :header-rows: 1
175+ :widths: 50 37
176+
177+ * - Macro
178+ - Event
179+ * - .. c:macro:: PY_MONITORING_EVENT_BRANCH_LEFT
180+ - :monitoring-event:`BRANCH_LEFT`
181+ * - .. c:macro:: PY_MONITORING_EVENT_BRANCH_RIGHT
182+ - :monitoring-event:`BRANCH_RIGHT`
183+ * - .. c:macro:: PY_MONITORING_EVENT_CALL
184+ - :monitoring-event:`CALL`
185+ * - .. c:macro:: PY_MONITORING_EVENT_C_RAISE
186+ - :monitoring-event:`C_RAISE`
187+ * - .. c:macro:: PY_MONITORING_EVENT_C_RETURN
188+ - :monitoring-event:`C_RETURN`
189+ * - .. c:macro:: PY_MONITORING_EVENT_EXCEPTION_HANDLED
190+ - :monitoring-event:`EXCEPTION_HANDLED`
191+ * - .. c:macro:: PY_MONITORING_EVENT_INSTRUCTION
192+ - :monitoring-event:`INSTRUCTION`
193+ * - .. c:macro:: PY_MONITORING_EVENT_JUMP
194+ - :monitoring-event:`JUMP`
195+ * - .. c:macro:: PY_MONITORING_EVENT_LINE
196+ - :monitoring-event:`LINE`
197+ * - .. c:macro:: PY_MONITORING_EVENT_PY_RESUME
198+ - :monitoring-event:`PY_RESUME`
199+ * - .. c:macro:: PY_MONITORING_EVENT_PY_RETURN
200+ - :monitoring-event:`PY_RETURN`
201+ * - .. c:macro:: PY_MONITORING_EVENT_PY_START
202+ - :monitoring-event:`PY_START`
203+ * - .. c:macro:: PY_MONITORING_EVENT_PY_THROW
204+ - :monitoring-event:`PY_THROW`
205+ * - .. c:macro:: PY_MONITORING_EVENT_PY_UNWIND
206+ - :monitoring-event:`PY_UNWIND`
207+ * - .. c:macro:: PY_MONITORING_EVENT_PY_YIELD
208+ - :monitoring-event:`PY_YIELD`
209+ * - .. c:macro:: PY_MONITORING_EVENT_RAISE
210+ - :monitoring-event:`RAISE`
211+ * - .. c:macro:: PY_MONITORING_EVENT_RERAISE
212+ - :monitoring-event:`RERAISE`
213+ * - .. c:macro:: PY_MONITORING_EVENT_STOP_ITERATION
214+ - :monitoring-event:`STOP_ITERATION`
215+ * - .. c:macro:: PY_MONITORING_EVENT_BRANCH
216+
217+ .. deprecated:: 3.14
218+ Use :c:macro:`PY_MONITORING_EVENT_BRANCH_LEFT`
219+ and :c:macro:`PY_MONITORING_EVENT_BRANCH_RIGHT` instead.
220+
221+ - :monitoring-event:`BRANCH_LEFT` and :monitoring-event:`BRANCH_RIGHT`
222+
195223
196224.. c:function:: int PyMonitoring_ExitScope(void)
197225
0 commit comments