Well it did turn out to be a general Python problem, or at least not a Stackless issue. It looks like if I slap PyEval_InitThreads() in my module declarations, it shuts the problem right up.
I wasn't "really" using Stackless, but the stack trace looked like it was running me through some Python code that had been altered for Stackless, so my sense of smell took me off that way. On Tue, Mar 13, 2012 at 1:53 PM, Richard Tew <[email protected]>wrote: > > > You're not really using Stackless. The loop with the schedule call > will just loop doing nothing. Looks like a general Python problem to > me. > > Cheers, > Richard. > > _______________________________________________ > Stackless mailing list > [email protected] > http://www.stackless.com/mailman/listinfo/stackless >
_______________________________________________ Stackless mailing list [email protected] http://www.stackless.com/mailman/listinfo/stackless
