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 pitrou
Recipients akuchling, djarb, facundobatista, forest, giampaolo.rodola, gvanrossum, intgr, j1m, jafo, josiahcarlson, kevinwatters, markb, mcdonc, pitrou, r.david.murray, stutzbach, tseaver
Date 2010-04-30.13:20:29
SpamBayes Score 0.07276757
Marked as misclassified No
Message-id <1272633633.63.0.0340083379776.issue1641@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with the points raised against Josiah's patch. I'm not sure O(n) cancellation is really a concern. The main focus of optimization should be the scheduler's loop itself, and both approaches have an O(log n) complexity there AFAICT. Also, the cancellation optimization could be backported into Giampaolo's patch.

One area tests should check for is when scheduling operations are done from a delayed call. Especially, a delayed call rescheduling itself.

By the way, it's too late for 2.7, so this is only for 3.2 now.
History
Date User Action Args
2010-04-30 13:20:34pitrousetrecipients: + pitrou, gvanrossum, akuchling, facundobatista, jafo, josiahcarlson, tseaver, forest, giampaolo.rodola, kevinwatters, djarb, stutzbach, markb, r.david.murray, intgr, mcdonc, j1m
2010-04-30 13:20:33pitrousetmessageid: <1272633633.63.0.0340083379776.issue1641@psf.upfronthosting.co.za>
2010-04-30 13:20:30pitroulinkissue1641 messages
2010-04-30 13:20:30pitroucreate