Author gvanrossum
Recipients akuchling, djarb, facundobatista, forest, giampaolo.rodola, gvanrossum, jafo, josiahcarlson, markb
Date 2009-03-03.18:44:26
SpamBayes Score 4.97411e-08
Marked as misclassified No
Message-id <1236105868.9.0.755689026045.issue1641@psf.upfronthosting.co.za>
In-reply-to
Content
The idea is to be able (whether you see a use case or not) to use
different tasks lists simultaneously.  Messing with globals is the worst
possible API for that.  All you need is to add a tasks=None argument to
the loop() signature, rename the global tasks list to (e.g.)
default_tasks, and add this to the top of loop:

if tasks is None:
    tasks = default_tasks

similar to what it does for map.  You'd also have to pass the tasks list
to the scheduler() call and the call_later() constructor.  Defaulting to
a global is fine.
History
Date User Action Args
2009-03-03 18:44:29gvanrossumsetrecipients: + gvanrossum, akuchling, facundobatista, jafo, josiahcarlson, forest, giampaolo.rodola, djarb, markb
2009-03-03 18:44:28gvanrossumsetmessageid: <1236105868.9.0.755689026045.issue1641@psf.upfronthosting.co.za>
2009-03-03 18:44:26gvanrossumlinkissue1641 messages
2009-03-03 18:44:26gvanrossumcreate