Potential Windows-specific lost event race in the implementation of time.sleep

Bug description:

In the Windows-specific implementation of time.sleep there appears this code:

https://github.com/python/cpython/blob/b706ff003c536c5bca24dfdd3a8917bffcfa3df1/Modules/timemodule.c#L2341-L2345

If a control-C event happens after PyErr_CheckSignals returns, but before ResetEvent is called, I believe that event may be lost.

This is probably a hard race window to hit, and I don't have a Windows development environment, so I have not confirmed that it is possible.

CPython versions tested on:

CPython main branch

Operating systems tested on:

Windows

リンク先の行にある Modules/timemodule.c の Windows 固有の time.sleep 実装から始め、次に PyErr_CheckSignals と ResetEvent の順序を調べてください。Windows でその間に control-C イベントが発生する可能性があるかを調査してください。失われたイベントの競合状態を確認または否定し、該当する場合はカバレッジを追加して動作を文書化または修正できれば完了です。