Hello. I have went and replaced Python threads with explicitly-scheduled coroutines using swapcontext() family of functions (basically out of frustration with the greenlet). I have two questions. 1. Is it as dangerous to switch C stacks and not switch PyThreadState as I suspect? In particular, how tightly is PyThreadState::frame coupled to current C stack? 2. How do you all look at merging my work as another threading-related configure switch? It's only another thread_something.h file and a small patch to threadmodule.c. Project is at http://code.google.com/p/coev/ -- ./lxnt
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