LoopingCall lacks reactor argument

[email protected] Mon, 15 Feb 2010 18:45:40 -0000
Newsgroups gmane.comp.python.twisted.bugs
Message-ID <[email protected]>
New submission from teamnoir <None>:

The doc for twisted.internet.task.LoopingCall is ambiguous.  It's not clear whether it intends to document a "clock" argument to __init__ or whether it intends to document an instance variable.  In any case, there should be a way to pass my reactor to LoopingCall as part of the initialization, without forcing the global reactor to be initialized.

Fixing this looks like it will require changing the calling convention of LoopingCall, (which might be why it hasn't been done already), so I haven't included a patch.

----------
Type     : defect
Component: core
Keywords : 
Priority : normal
Nosy     : 
----------
http://twistedmatrix.com/trac/ticket/4276