From 5b08fae0b993552a4ff3d02275bb815512dd1498 Mon Sep 17 00:00:00 2001 From: Hood Chatham Date: Sun, 19 Jul 2026 15:39:36 +0200 Subject: [PATCH] gh-145559: Make PyUnstable_DumpTraceback void return In gh-148145, we changed this to return a const char* but it is always NULL. I don't think this makes sense, so this puts it back. --- Python/traceback.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Python/traceback.c b/Python/traceback.c index 5bfa28f9c7dc8b6..9e58b9055ad816c 100644 --- a/Python/traceback.c +++ b/Python/traceback.c @@ -1167,11 +1167,10 @@ dump_traceback(int fd, PyThreadState *tstate, int write_header) The caller is responsible to call PyErr_CheckSignals() to call Python signal handlers if signals were received. */ -const char* +void PyUnstable_DumpTraceback(int fd, PyThreadState *tstate) { dump_traceback(fd, tstate, 1); - return NULL; } #if defined(HAVE_PTHREAD_GETNAME_NP) || defined(HAVE_PTHREAD_GET_NAME_NP)