[issue43356] PyErr_SetInterrupt should have an equivalent that takes a signal number

Change by Antoine Pitrou : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue43356] PyErr_SetInterrupt should have an equivalent that takes a signal number

Antoine Pitrou added the comment: New changeset ba251c2ae6654bfc8abd9d886b219698ad34ac3c by Antoine Pitrou in branch 'master': bpo-43356: Allow passing a signal number to interrupt_main() (GH-24755) https://github.com/python/cpython/commit/ba251c2ae6654bfc8abd9d886b219698ad34ac3c

[issue43356] PyErr_SetInterrupt should have an equivalent that takes a signal number

Change by Antoine Pitrou : -- keywords: +patch pull_requests: +23526 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24755 ___ Python tracker ___

[issue43356] PyErr_SetInterrupt should have an equivalent that takes a signal number

Change by Antoine Pitrou : -- nosy: +neologix, vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43356] PyErr_SetInterrupt should have an equivalent that takes a signal number

New submission from Antoine Pitrou : PyErr_SetInterrupt() is useful if you want to simulate the effect of a SIGINT. It would be helpful to provide a similar primitive for other signal numbers, e.g. `PyErr_SetInterruptEx(int signum)`. -- components: C API messages: 387877 nosy: pitrou