OK, thanks. The coroutine should get rescheduled when the print is complete, right?
I was having an issue where I was spawning the coroutine, then it was blocking on the info() and never being rescheduled. I haven't been able to reproduce it in a minimal example, so it's possible something else was going on. Strangely, when I remove the "info"s and let the coroutine get to the point where it explicitly waits on a file descriptor, it seems to get rescheduled as expected when the FD becomes available. peace, s On Mon, Jun 23, 2014 at 4:13 PM, Jameson Nash <[email protected]> wrote: > Yes. Any use of I/O may block a coroutine and allow other tasks to run. > > > On Monday, June 23, 2014, Spencer Russell <[email protected]> wrote: > >> I'm debugging some coroutine concurrency stuff and using info() to spit >> out debugging info during execution. >> >> I'm getting some confusing results (My coroutine is blocking when I don't >> expect it to), so I wanted to check if printing to stdout ever causes a >> coroutine to block. >> >> peace, >> s >> >
