Message331810
| Author | pitrou |
|---|---|
| Recipients | davin, pablogsal, pitrou, vstinner |
| Date | 2018-12-14.12:08:59 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1544789339.45.0.788709270274.issue35493@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> I have to investigate how Process.sentinel can be used here. Look how concurrent.futures uses it: https://github.com/python/cpython/blob/master/Lib/concurrent/futures/process.py#L348 This also means: 1) we could redirect people to ProcessPoolExecutor instead of trying to backport all its features into multiprocessing.Pool 2) we could try to refactor the ProcessPoolExecutor implementation into a common backend for both ProcessPoolExecutor and multiprocessing.Pool |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-12-14 12:08:59 | pitrou | set | recipients: + pitrou, vstinner, davin, pablogsal |
| 2018-12-14 12:08:59 | pitrou | set | messageid: <1544789339.45.0.788709270274.issue35493@psf.upfronthosting.co.za> |
| 2018-12-14 12:08:59 | pitrou | link | issue35493 messages |
| 2018-12-14 12:08:59 | pitrou | create | |