Mark Hammond wrote: > But what if in some cases, this callback is as a result of Python code on > the same thread - ie, there already exists a Python thread-state higher up > the stack? Then you get a deadlock. However, it was not your (stated) goal to support this case. You mentioned threads that Python had never seen before - there can't be a thread state higher up in such a thread. 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