Earlier quoted context omitted.
"Hard to read" is subjective; many Twisted afficionados, myself included, strongly disagree. What impact do you feel the destruction of locality has, specifically? Do you feel @inlineCallbacks and Corotwine answer these issues?
Destroying locality makes the program very difficult to read for anyone other than the person who wrote it. I've been there before and done that. I've written Z80 assembly code where functions had more than one entry point as well as exit point. Sometimes I didn't bother to keep a stack at all. Spaghetti code. I was proud of it at the time. Not so much now. My understanding of Corotwine and greenlet is that they're b…
http://thread.gmane.org/gmane.comp.python.devel/136422
This will certainly improve the situation with interfacing different Python libraries together if it gets adopted. I still don't think asynchronous APIs are as easy to use as blocking ones, but I guess I've said enough about that already :)