I'm using py3k so gevent isn't really an option. Is there any sort of debugging message mechanism to try to figure out what's going wrong?
I was thinking of creating a simplified example to demonstrate the issue, but I don't think I can help with the issue beyond that. On Tue, Feb 17, 2015 at 3:15 PM, Roberto De Ioris <[email protected]> wrote: > > > Caveat: not a uWSGI contributor, and I'm responding since this problem > > sounds interesting, not because I know much about it... > > > > My understanding is that `yield` only makes sense in this context if your > > app is a generator function you've written yourself and passed to uWSGI > > directly (AFAIK this is kind of an extension to the WSGI spec: it's > > supposed to return an iterator, not be a generator itself...?). If you're > > using a framework like Pyramid then you'll always be too far down the > call > > stack (aka "anywhere but the very top") for `yield` to trigger uWSGI's > > async behavior. > > > > So the point of `uwsgi.suspend()` is to trigger that behavior if you're > > further down the call stack, aka all the time if you're using a > framework. > > Now, why that's not working correctly, I have no idea. > > > > > > Yes, uwsgi.suspend() is a more brutal way for when yield cannot be used. > > Having said that, the low-level async mode is really low-level, plugins > like gevent (or coroae) are build on top of it so it is generally better > to use them. > > > -- > Roberto De Ioris > http://unbit.com > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
