LoopingCall lacks reactor argument

	teamnoir reported
Trac ID	trac#4276
Type	defect
Created	2010-02-15 18:45:40Z

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.

trac-id__4276 4276
type__defect defect
reporter__teamnoir teamnoir
priority__normal normal
milestone__ 
branch__ 
branch_author__ 
status__new new
resolution__None None
component__core core
keywords__ 
time__1266259540000000 1266259540000000
changetime__1266370337000000 1266370337000000
version__None None
owner__ 

Start with the documentation and init API for twisted.internet.task.LoopingCall, then trace how it obtains the reactor and check the existing calling convention. Done means the intended clock or reactor argument is unambiguous and can be supplied during initialization without forcing the global reactor to initialize.