[issue40912] _PyOS_SigintEvent is never closed on Windows

STINNER Victor added the comment: Fixed by bpo-41686: commit 0ae323b87f1bed64a7fa70f5a41a5800aca032cc Author: Victor Stinner Date: Tue Nov 17 18:15:20 2020 +0100 bpo-41686: Always create the SIGINT event on Windows (GH-23344) bpo-41686, bpo-41713: On Windows, the SIGINT

[issue40912] _PyOS_SigintEvent is never closed on Windows

Dong-hee Na added the comment: @vstinner https://github.com/python/cpython/blob/ae0a2b756255629140efcbe57fc2e714f0267aa3/Modules/signalmodule.c#L1743 Since _PySignal_Fini close the handle, IMHO we can close this issue. Is there any corner case to handle this? --

[issue40912] _PyOS_SigintEvent is never closed on Windows

Change by Dong-hee Na : -- nosy: +corona10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40912] _PyOS_SigintEvent is never closed on Windows

Change by Tim Golden : -- assignee: -> tim.golden ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40912] _PyOS_SigintEvent is never closed on Windows

STINNER Victor added the comment: PyOS_FiniInterrupts() is a good place to close _PyOS_SigintEvent. Hopefully, it's a internal C API and it's not exported, since it's fine to change its behavior. Maybe it should be renamed to _PyOS_FiniInterrupts(). --

[issue40912] _PyOS_SigintEvent is never closed on Windows

New submission from Steve Dower : Currently, it's just stored as global state in signalmodule.c and forgotten about. It probably needs to become module state, and the signal module needs better initialization/shutdown. -- components: Windows messages: 371036 nosy: eric.snow,