[Twisted-Python] Shutdown empty reactor?

Itamar Shtull-Trauring itamar at itamarst.org
Fri Jul 11 13:57:03 EDT 2003

On Fri, 11 Jul 2003 12:18:42 -0400
"Phillip J. Eby" <pje at telecommunity.com> wrote:

> Is this something that could be added, or is there any general
> interest in having idle reactors shut down?  In principle, there is no
> way for a running-on-empty reactor to do any further useful work, and
> no way for it to be shut down, either.  (If one is using threads, then
> there is always a "waker" selectable present, which means that by
> definition a reactor using threads is never "running on empty".)

There may be scheduled calls (and some of these are module level, e.g.
http and thus always present if that module is imported).

There may be a GUI connected to the event loop.

Users should probably track their, say, client connections if that's
what they're doing and shutdown the reactor manually.

Itamar Shtull-Trauring    http://itamarst.org/
http://www.zoteca.com -- Python & Twisted consulting

More information about the Twisted-Python mailing list