On Wed, Mar 14, 2012 at 3:57 AM, Adam Preble <[email protected]> wrote: > I put in double effort to get this out in the morning because of the volume > of response I got on the topic yesterday. I am wondering now if this is > truly a Stackless Python issue. I need to try linking this to legacy Python > too, but I rushed on the code to at least have something to show to those > whose interest was piqued yesterday. Normally I post anything with > interoperability in it to the cplusplus-sig where the Boost.Python people > hang out, but the stack trace for the PyThreadState_get call is in the > Python stack, not through my code. So I figure it's a runtime issue of some > kind--whether Stackless or conventional Python. >
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
