James Mills

In that case I recommend we seriously reconsider the architecture of circuits.web -- even breaking it's user-facing API a bit? James Mills / prologic E: [email protected] W: prologic.shortcircuit.net.au On Sun,...

Ahh I was doing some Github cleanup! Sorry, do you want to take over the branch/PR?

:+1: Worth looking in to :) I suspect it _might_ have something to do with the fact that coroutines are handled in the "next tick" so to speak; whereas fired...

With a much simpler implementation of this "slow test": ``` #!python from circuits import Component, Event class counter(Event): """counter Event""" complete = True class Slow(Component): def started(self, *args): # self.fire(counter(10))...

Hmm I'll have to study your _contrived example_ a bit more :) I'm not quite following it yet :)

Yeah okay I see :) I'll have to play with this some more and see what's going on. To be honest I'm not sure why you're using coroutines (_or were...

Ahh so in your particular case you were calling the wrong API method? `yield self.wait()` is indeed **NOT** equivalent to `self.call()` :) Both in effect create coroutines!

Yeah so `call/wait` are essentially the same. `.call()` does a `.fire()` and `.wait()`, whilst `.wait()` only wiats for an event's completion. Both are used to write synchronous code that is...

Any further thoughts/comments on this? Do we need to change/fix/update anything here? Improve the documentation around this perhaps?

@spaceone Do you have any thoughts on improving this at all -- Or should we just document it better? `call/wait` provide coroutines (_cooperative threading_); I would never expect them to...