Martin v. Löwis wrote: > Can you please explain what you mean by "swallowing"? The signals don't get through when acquiring the lock. > What is the sequence of actions triggering the case you are talking > about, what happens, and what do you expect to happen instead? Create a Lock object, call .acquire and try to press Ctrl-C, the keyboardinterrupt is swallowed > Also, how would you fix this (in principle, not what the specific > patch would look like)? Remove the loop that explicitly does this in a new function and use that one in threadmodule.c for lock.acquire. > > Regards, > Martin Best regards, Florian PS: Sorry for sending this message twice.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4