Hi,

time.sleep() function is not working on Windows host if I use C API Py_InitializeEx(0) function.

Issue could be reproduce with following simple example.

int main()
{
   Py_InitializeEx(0);
   PyRun_SimpleString("import time \n"
		      "start = time.time() \n"
		      "time.sleep(4) \n"
		      "print('elapsed: %d' % (time.time() - start))");
}

output:

elapsed: 0


Note, issue is not reproduce on Linux host.

The SIGINT event gets created when the _signal extension module is imported. Until then, _PyOS_SigintEvent() returns NULL. But currently all code that calls _PyOS_SigintEvent() assumes it returns a valid handle. This has to be fixed to support Py_InitializeEx(0). 

For example, pysleep could call WinAPI Sleep on the main thread if the interrupt event isn't configured:

        ul_millis = (unsigned long)millisecs;
        hInterruptEvent = _PyOS_SigintEvent();

        if (ul_millis == 0 || !hInterruptEvent || !_PyOS_IsMainThread()) {
            Py_BEGIN_ALLOW_THREADS
            Sleep(ul_millis);
            Py_END_ALLOW_THREADS
            break;
        }

Py_InitializeEx() should be modified to always initialize sigint_event, even if install_sigs is equal to zero.

Maybe the variable should be moved somewhere else. Maybe in the time module?

By the way, it would be nice to add error handling on:

    sigint_event = CreateEvent(NULL, TRUE, FALSE, FALSE);


See also PR #22049.

> Maybe in the time module?

The SIGINT event is also needed by PyOS_Readline, _io (builtin), _winapi (builtin), and _multiprocessing (pyd). Is the time module guaranteed to be imported in 3.x? It appears to get imported incidentally via _PyImportZip_Init (zipimport). 

Could sigint_event be relocated to a platform-dependent extension of _PyRuntimeState that gets initialized and finalized independent of any module?

> Could sigint_event be relocated to a platform-dependent extension of _PyRuntimeState that gets initialized and finalized independent of any module?

This, or leaving it where it is and making sure it gets initialised (it really is about emulating certain signals). Either sounds fine to me.

New changeset 0ae323b87f1bed64a7fa70f5a41a5800aca032cc by Victor Stinner in branch 'master':
bpo-41686: Always create the SIGINT event on Windows (GH-23344)
https://github.com/python/cpython/commit/0ae323b87f1bed64a7fa70f5a41a5800aca032cc

New changeset cda23be092f4a72e4f335cf182f11e7bd7fd98eb by Victor Stinner in branch 'master':
bpo-41686: Refactor signal_exec() (GH-23346)
https://github.com/python/cpython/commit/cda23be092f4a72e4f335cf182f11e7bd7fd98eb

New changeset 05a5d697f4f097f37c5c1e2ed0e2338a33c3fb6a by Victor Stinner in branch '3.9':
bpo-41686: Always create the SIGINT event on Windows (GH-23344) (GH-23347)
https://github.com/python/cpython/commit/05a5d697f4f097f37c5c1e2ed0e2338a33c3fb6a

New changeset a702bd4b921167e73f8fc987aa64ada571fdc3f8 by Victor Stinner in branch '3.8':
bpo-41686: Always create the SIGINT event on Windows (GH-23344) (GH-23347) (GH-23349)
https://github.com/python/cpython/commit/a702bd4b921167e73f8fc987aa64ada571fdc3f8

Ok, the issue should now be fixed in 3.8, 3.9 and master branches. Thanks for the bug report hafiz bilal.

New changeset 29aa624047f893b3b3194f00252b2156bbbf4f9b by Victor Stinner in branch 'master':
bpo-41686: Move _Py_RestoreSignals() to signalmodule.c (GH-23353)
https://github.com/python/cpython/commit/29aa624047f893b3b3194f00252b2156bbbf4f9b

> bpo-41686: Move _Py_RestoreSignals() to signalmodule.c (GH-23353)

Sorry, this change was for bpo-41713.

stage: patch review -> resolved

messages: + msg376196

components: + Windows
type: behavior