Hi, I'm still to trying to figure out why the main thread is a special case in Tulip. For example, EventLoopPolicy.get_event_loop() only creates a new event loop when it is called from the main thread. Is it to avoid bugs?
Does it mean that I need to call explicitly policy.new_event_loop() and then policy.set_event_loop(loop) if I want to use a loop in a thread different than the main thread? _UnixDefaultEventLoopPolicy._init_watcher() does nothing if it is called from a thread different than the main thread. Does it mean that it is not possible to run an event loop running subprocesses from a thread diferent than the main thread? I can understand that only one event loop can install an handler sor SIGCHLD signal, but why not allowing to run it in a different thread? I just modified get_child_watcher() to add an optional loop parameter in my subprocess_stream branch, so it's possible to run unit tests with set_event_loop(None). http://code.google.com/p/tulip/source/detail?r=f9e077be6d3b97fde52b10131224d75696a0cbdf&name=subprocess_stream Victor
