Message148409
| Author |
giampaolo.rodola |
| Recipients |
giampaolo.rodola, josiahcarlson, mark.dickinson, pitrou |
| Date |
2011年11月26日.14:40:12 |
| SpamBayes Score |
0.00043371812 |
| Marked as misclassified |
No |
| Message-id |
<1322318413.09.0.831814810345.issue8684@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Looking back at this patch, I think we can extract the thread-synchronization parts and the peek() method, as they're both valuable additions, especially the first one.
The very sched doc says:
> In multi-threaded environments, the scheduler class has limitations
> with respect to thread-safety, inability to insert a new task before
> the one currently pending in a running scheduler, and holding up the
> main thread until the event queue is empty. Instead, the preferred
> approach is to use the threading.Timer class instead. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年11月26日 14:40:13 | giampaolo.rodola | set | recipients:
+ giampaolo.rodola, josiahcarlson, mark.dickinson, pitrou |
| 2011年11月26日 14:40:13 | giampaolo.rodola | set | messageid: <1322318413.09.0.831814810345.issue8684@psf.upfronthosting.co.za> |
| 2011年11月26日 14:40:12 | giampaolo.rodola | link | issue8684 messages |
| 2011年11月26日 14:40:12 | giampaolo.rodola | create |
|