Most "active" coroutine library project?

[Jason Tackaberry]

On Wed, 2009-09-23 at 21:53 +0000, exarkun at twistedmatrix.com wrote:
> I specifically left out all "yield" statements in my version, since 
> that's exactly the point here. :)  With "real" coroutines, they're not 
> necessary - coroutine calls look just like any other call.  With 
> Python's enhanced generators, they are.

Yes, I take your point.

Explicitly yielding may not be such a terrible thing, though.  It's more
clear when reading such code where it may return back to the scheduler.
This may be important for performance, unless of course the coroutine
implementation supports preemption.

Cheers,
Jason.