Use highest pickle protocol in multiprocessing

[ebehn]

BPO	26507
Nosy	@pitrou, @applio
Superseder	bpo-28053: parameterize what serialization is used in multiprocessing
Files	patch: Patch to fix issue patch: Patch to fix issue

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2016-09-09.21:02:12.025>
created_at = <Date 2016-03-08.02:11:24.804>
labels = ['extension-modules', 'type-feature']
title = 'Use highest pickle protocol in multiprocessing'
updated_at = <Date 2016-09-09.21:02:12.023>
user = 'https://bugs.python.org/ebehn'

bugs.python.org fields:

activity = <Date 2016-09-09.21:02:12.023>
actor = 'davin'
assignee = 'none'
closed = True
closed_date = <Date 2016-09-09.21:02:12.025>
closer = 'davin'
components = ['Extension Modules']
creation = <Date 2016-03-08.02:11:24.804>
creator = 'ebehn'
dependencies = []
files = ['42086', '42087']
hgrepos = []
issue_num = 26507
keywords = []
message_count = 4.0
messages = ['261318', '261320', '261506', '275439']
nosy_count = 3.0
nosy_names = ['pitrou', 'davin', 'ebehn']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = None
status = 'closed'
superseder = '28053'
type = 'enhancement'
url = 'https://bugs.python.org/issue26507'
versions = ['Python 3.6']

[ebehn]

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.

[applio]

As described in bpo-23403, 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.

[pitrou]

Agreed with Davin.

[applio]

Closing in deference to the enhancement described in bpo-28053.