> Now to my real question. I have noticed that PyThread_acquire_lock > swallows all signals with pthread using sems. Looking at the source code > it appears that this is intended, but I cannot see the reason for that. > It seems the pthread sem implementation is the only one doing so. Can > any of you tell me the reason why it swallows signals? Can you please explain what you mean by "swallowing"? What is the sequence of actions triggering the case you are talking about, what happens, and what do you expect to happen instead? Also, how would you fix this (in principle, not what the specific patch would look like)? Regards, Martin
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