Message 132660 - Python tracker
Message132660
| Author | pitrou |
|---|---|
| Recipients | Albert.Strasheim, aljungberg, asksol, bquinlan, gdb, hongqn, jnoller, pitrou, vlasovskikh, vstinner |
| Date | 2011-03-31.12:25:37 |
| SpamBayes Score | 1.609831e-06 |
| Marked as misclassified | No |
| Message-id | <1301574338.12.0.437023762009.issue9205@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The problem with this approach is that it won't help concurrent.futures. Detection of killed endpoints should ideally happen at a lower level, e.g. in Process or Queue or Connection objects. Speaking of which, I wonder why we have both multiprocessing.Pool and concurrent.futures.ProcessPoolExecutor. They seem to fill the exact same needs, with different APIs... |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-03-31 12:25:38 | pitrou | set | recipients: + pitrou, bquinlan, vstinner, jnoller, hongqn, asksol, vlasovskikh, gdb, Albert.Strasheim, aljungberg |
| 2011-03-31 12:25:38 | pitrou | set | messageid: <1301574338.12.0.437023762009.issue9205@psf.upfronthosting.co.za> |
| 2011-03-31 12:25:37 | pitrou | link | issue9205 messages |
| 2011-03-31 12:25:37 | pitrou | create | |