This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jyasskin
Recipients BreamoreBoy, aminusfu, jyasskin, loewis, pitrou, sonderblade
Date 2010-09-16.23:42:08
SpamBayes Score 1.4575845e-06
Marked as misclassified No
Message-id <1284680535.83.0.13218038411.issue1676820@psf.upfronthosting.co.za>
In-reply-to
Content
Java's Timer class tends to be discouraged these days in favor of ScheduledExecutorService.scheduleAtFixedRate and .scheduleWithFixedDelay (http://download.oracle.com/javase/7/docs/api/java/util/concurrent/ScheduledExecutorService.html). Could you say why you modeled this interface off of java.util.Timer instead of ScheduledExecutor? See http://www.python.org/dev/peps/pep-3148/ for the basis of executors in Python.

I'm skeptical of having a PeriodicTimer that embeds a fixed-delay timing. Both fixed-rate and fixed-delay are useful for different things, and given the ambiguity we probably shouldn't give in to the temptation to guess. 

I'm skeptical of having a new thread per periodic task. It's a little more work to multiplex tasks onto shared threads, and maybe that work isn't worth it for now, but I think the interface should allow future implementations to multiplex their tasks.
History
Date User Action Args
2010-09-16 23:42:16jyasskinsetrecipients: + jyasskin, loewis, sonderblade, aminusfu, pitrou, BreamoreBoy
2010-09-16 23:42:15jyasskinsetmessageid: <1284680535.83.0.13218038411.issue1676820@psf.upfronthosting.co.za>
2010-09-16 23:42:09jyasskinlinkissue1676820 messages
2010-09-16 23:42:08jyasskincreate