Nick Coghlan schrieb:
Stephen J. Turnbull wrote:
Discussion of how to spell SIGKILL looks like bikeshed painting to me, but the question of how to extend graceful interrupt behavior to C modules looks worthy of an idea to me.
Is that too hard or too rare a need?
If someone can come up with an adequate C API spelling of the change (e.g. a PYTHON_BEGIN_ALLOW_SIGINT_ABORT/PYTHON_END_ALLOW_SIGINT_ABORT) and define it in such a way that the burden for cleaning up before resumption of execution of Python code is placed on the developer using the new API then I'd be +1.
Do you think people would use it? It's already hard to convince them of using the thread state macros correctly, and the benefit of doing that is subjectively much larger (multithreading works without blocking) than for the SIGINT handling. Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out.