bpo-26558: Fix Py_FatalError() with GIL released (GH-10267)


Don't call _Py_FatalError_PrintExc() nor flush_std_files() if the
current thread doesn't hold the GIL, or if the current thread
has no Python state thread.
(cherry picked from commit 3a228ab17c2a9cffd1a2f15f30d6209768de20a6)

Co-authored-by: Victor Stinner <vstinner@redhat.com>
1 file changed