Eli Zaretskii writes: >> From: Tom Tromey >> Cc: gdb-patches@sourceware.org >> Date: Fri, 17 Oct 2025 08:13:14 -0600 >> >> >>>>> "Tom" == Tom de Vries writes: >> >> Tom> The problem doesn't happen if we use the PyConfig approach instead of the >> Tom> py_initialize_catch_abort approach. >> >> Tom> Fix this by using the PyConfig approach starting 3.9 (previously, starting >> Tom> 3.10 to avoid Py_SetProgramName deprecation in 3.11). >> >> Seems fine to me. >> >> Tom> It's possible that we have the same problem and need the same fix for 3.8, but >> Tom> I don't have a setup to check that. Add a todo in a comment. >> >> I wonder if anyone even uses that version. It has been EOL'd. > > We still support Python 3.4, because that's the only version available > on Windows XP. Why does that matter? We shouldn't hold back development of free software for sake of a long-abandoned proprietary operating system. -- Arsen Arsenović