➜
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.
Created on 2016-03-08 02:11 by ebehn, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| patch | ebehn, 2016-03-08 02:11 | Patch to fix issue | review | |
| patch | ebehn, 2016-03-08 02:14 | Patch to fix issue | review | |
| Messages (4) | |||
|---|---|---|---|
| msg261318 - (view) | Author: Ed Behn (ebehn) * | Date: 2016-03-08 02:11 | |
Currently, the default pickle protocol is used to return worker results in a multiprocessing pool. The highest protocol should be used because backwards compatibility is not an issue. |
|||
| msg261320 - (view) | Author: Davin Potts (davin) *  |
Date: 2016-03-08 03:49 | |
As described in issue23403, it is possible for independent processes to communicate to one another through multiprocessing. Thus changing the default triggers complications and is arguably much less interesting than having control over what protocol (or mechanism) is to be used for pickling. |
|||
| msg261506 - (view) | Author: Antoine Pitrou (pitrou) * |
Date: 2016-03-10 15:24 | |
Agreed with Davin. |
|||
| msg275439 - (view) | Author: Davin Potts (davin) * |
Date: 2016-09-09 21:02 | |
Closing in deference to the enhancement described in issue28053. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:28 | admin | set | github: 70694 |
| 2016-09-09 21:02:12 | davin | set | status: open -> closed superseder: parameterize what serialization is used in multiprocessing resolution: duplicate messages: + msg275439 |
| 2016-03-10 15:24:40 | pitrou | set | nosy:
+ pitrou messages: + msg261506 |
| 2016-03-08 03:49:00 | davin | set | nosy:
+ davin messages: + msg261320 |
| 2016-03-08 02:14:23 | ebehn | set | files: + patch |
| 2016-03-08 02:11:24 | ebehn | create | |