From d8fedf21cc7f6ba61e77db21de0eb9892545d34f Mon Sep 17 00:00:00 2001 Message-Id: From: Mark Wooding Date: Sun, 19 May 2013 19:36:52 +0100 Subject: [PATCH] py/tripe.py.in: Sort out the `SelIOWatcher.iterate' commentary. Organization: Straylight/Edgeware From: Mark Wooding It's not strictly true that `SelIOWatcher.iterate' isn't used by `TripeCommandDispatcher', because the latter's `mainloop' method calls it; but that's not something you need to care about unless you're also using the service implementation framework. --- py/tripe.py.in | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/py/tripe.py.in b/py/tripe.py.in index ac616ae8..ae88ba3d 100644 --- a/py/tripe.py.in +++ b/py/tripe.py.in @@ -330,8 +330,10 @@ class SelIOWatcher (object): Wait for something interesting to happen, and issue events. That is, basically, do one iteration of a main select loop, processing - all of the events, and then return. This isn't needed for - `TripeCommandDispatcher', but `runservices' wants it. + all of the events, and then return. This is used in the method + `TripeCommandDispatcher.mainloop', but that's mostly for the benefit of + `runservices'; if your I/O watcher has a different main loop, you can + drive it yourself. """ M.select() -- [mdw]