Logged In: YES 
user_id=1038590

Patch #1044089 has been created with an alternate
implementation of the same concept. Rather than using
_PyThread_Started, it:

- uses interpreter_lock within ceval.c, which matches the
existing ceval.c code that uses the existence of the GIL to
determine if PyEval_InitThreads has been called
- adds a new API function PyEval_ThreadsInitialized which
allows external code to check if the GIL exists or not
- uses this new API in the PyGILState_* functions

The same functions get modified as in the patch attached
here - the only difference is in how the code asks the
question "Has PyEval_InitThreads been called?"