Jason Tackaberry wrote: > On Thu, 2008-08-07 at 19:58 +0200, Dirk Meyer wrote: >> I never liked the fact that you import async.py in the function :) > > We do it all over the place, not just there.
We shouldn't ;) > I realize it's a bit icky, but then it's a quite well understood > solution to cyclical imports. Maybe we don't need to, see below... >> First of all, I have to check a lot of code where it could be a >> problem. So you should add a deprecated warning first. Besides that, I >> don't like async. Maybe wait? > > I'm happy to rename async, but not to wait. Because InProgress has a > wait method, so this is pretty dumb: > > signal.wait().wait() OK, that is ugly. Besides the fact that I never liked the wait(), maybe we can add Signals support to coroutine itself. If a functions yields a Signal we wrap it. On the downside you can never "return" a Signal from a coroutine. Dischi -- Bills travel through the mail at twice the speed of checks. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
