From 94515cd8a0a9e6bff26434a0b551c9bef892323f Mon Sep 17 00:00:00 2001 From: manoj Date: Sun, 31 May 2026 21:39:44 +0530 Subject: [PATCH 1/5] Fix typos in exceptions.rst under PyUnstable_DumpTracebackThreads() --- Doc/c-api/exceptions.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst index fd9ea6272df7d8..d4cf42c6f18e62 100644 --- a/Doc/c-api/exceptions.rst +++ b/Doc/c-api/exceptions.rst @@ -1385,14 +1385,14 @@ Tracebacks interpreter using thread-specific storage. If it cannot, it will return an error. - If *current_tstate* is not ``NULL`` then it will be used to identify what the + If *current_tstate* is not ``NULL`` then it will be used to identify which current thread is in the written output. If it is ``NULL`` then this function will identify the current thread using thread-specific storage. It is not an error if the function is unable to get the current Python thread state. This function will return ``NULL`` on success, or an error message on error. - This function is meant to debug debug situations such as segfaults, fatal + This function is meant to debug situations such as segfaults, fatal errors, and similar. It calls :c:func:`PyUnstable_DumpTraceback` for each thread. It only writes the tracebacks of the first *max_threads* threads, further output is truncated with the line ``...``. If *max_threads* is 0, the From 06421770b854649c9f0effd48c86e4ccbabcd1a3 Mon Sep 17 00:00:00 2001 From: manoj Date: Sun, 31 May 2026 21:42:35 +0530 Subject: [PATCH 2/5] Fix Possible Lint issue --- Doc/c-api/exceptions.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst index d4cf42c6f18e62..e7b05bd3edda8a 100644 --- a/Doc/c-api/exceptions.rst +++ b/Doc/c-api/exceptions.rst @@ -1385,7 +1385,7 @@ Tracebacks interpreter using thread-specific storage. If it cannot, it will return an error. - If *current_tstate* is not ``NULL`` then it will be used to identify which + If *current_tstate* is not ``NULL`` then it will be used to identify which current thread is in the written output. If it is ``NULL`` then this function will identify the current thread using thread-specific storage. It is not an error if the function is unable to get the current Python thread state. From 93fdd3382d2630c76428ab64ef888047a838203c Mon Sep 17 00:00:00 2001 From: manoj Date: Mon, 1 Jun 2026 15:48:50 +0530 Subject: [PATCH 3/5] revert changes on the first sentence --- Doc/c-api/exceptions.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst index e7b05bd3edda8a..c67e1957a72988 100644 --- a/Doc/c-api/exceptions.rst +++ b/Doc/c-api/exceptions.rst @@ -1385,7 +1385,7 @@ Tracebacks interpreter using thread-specific storage. If it cannot, it will return an error. - If *current_tstate* is not ``NULL`` then it will be used to identify which + If *current_tstate* is not ``NULL`` then it will be used to identify what the current thread is in the written output. If it is ``NULL`` then this function will identify the current thread using thread-specific storage. It is not an error if the function is unable to get the current Python thread state. From c67a9df03a8aeac483db7beeba111a5c82ff02b3 Mon Sep 17 00:00:00 2001 From: manoj Date: Mon, 1 Jun 2026 19:22:02 +0530 Subject: [PATCH 4/5] fix minor typos in exceptions.rst --- Doc/c-api/exceptions.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst index c67e1957a72988..f5c63dd02fca88 100644 --- a/Doc/c-api/exceptions.rst +++ b/Doc/c-api/exceptions.rst @@ -303,7 +303,7 @@ For convenience, some of these functions will always return a Set file, line, and offset information for the current exception. If the current exception is not a :exc:`SyntaxError`, then it sets additional - attributes, which make the exception printing subsystem think the exception + attributes, which make the exception printing subsystem to think that the exception is a :exc:`SyntaxError`. .. versionadded:: 3.4 @@ -412,7 +412,7 @@ an error value). .. c:function:: int PyErr_WarnFormat(PyObject *category, Py_ssize_t stack_level, const char *format, ...) - Function similar to :c:func:`PyErr_WarnEx`, but use + Function similar to :c:func:`PyErr_WarnEx`, but uses :c:func:`PyUnicode_FromFormat` to format the warning message. *format* is an ASCII-encoded string. From fb9ba6c4ca4c0e660d49eb72af99c3a2b27abe15 Mon Sep 17 00:00:00 2001 From: manoj Date: Mon, 1 Jun 2026 19:30:19 +0530 Subject: [PATCH 5/5] fix minor typos in exceptions.rst --- Doc/c-api/exceptions.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/c-api/exceptions.rst b/Doc/c-api/exceptions.rst index f5c63dd02fca88..f3f408c400bed0 100644 --- a/Doc/c-api/exceptions.rst +++ b/Doc/c-api/exceptions.rst @@ -303,7 +303,7 @@ For convenience, some of these functions will always return a Set file, line, and offset information for the current exception. If the current exception is not a :exc:`SyntaxError`, then it sets additional - attributes, which make the exception printing subsystem to think that the exception + attributes, which make the exception printing subsystem think the exception is a :exc:`SyntaxError`. .. versionadded:: 3.4