[issue28053] parameterize what serialization is used in multiprocessing

Change by Pierre Glaser : -- pull_requests: +14807 pull_request: https://github.com/python/cpython/pull/15058 ___ Python tracker ___ ___

[issue28053] parameterize what serialization is used in multiprocessing

Change by Pablo Galindo Salgado : -- pull_requests: +9306 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue28053] parameterize what serialization is used in multiprocessing

Change by Pablo Galindo Salgado : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue28053] parameterize what serialization is used in multiprocessing

Change by Igor : -- nosy: +i3v ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman

[issue28053] parameterize what serialization is used in multiprocessing

Antoine Pitrou added the comment: I'd like to know if the work here will be completed soon :-) This currently lacks documentation but also tests. In particular, looking at the code (and that is supported by Will S' comment above), I feel the API isn't working as intended (i.e. setting the "re

[issue28053] parameterize what serialization is used in multiprocessing

Will S added the comment: Just to follow up in case anyone comes across my last message later: I just had to change the last line from multiprocessing.reducer = pickle2reducer.Pickle2Reducer() to multiprocessing.context._default_context.reducer = pickle2reducer.Pickle2Reducer() --

[issue28053] parameterize what serialization is used in multiprocessing

Will S added the comment: Documentation would be appreciated. I have a project that uses BaseManager, Client, and Listener to create some servers and clients. I would like to update the project to work with Python 3 and would prefer to update the clients and the servers separately (i.e. switch

[issue28053] parameterize what serialization is used in multiprocessing

Davin Potts added the comment: Docs need updating still. -- versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue28053] parameterize what serialization is used in multiprocessing

Roundup Robot added the comment: New changeset 7381b1b50e00 by Davin Potts in branch 'default': Issue #28053: Applying refactorings, docs and other cleanup to follow. https://hg.python.org/cpython/rev/7381b1b50e00 -- nosy: +python-dev ___ Python track

[issue28053] parameterize what serialization is used in multiprocessing

Eric Snow added the comment: LGTM -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/ma

[issue28053] parameterize what serialization is used in multiprocessing

Davin Potts added the comment: Attaching patch containing refactorizations but missing update to docs for the purposes of review. Introduces three new things: * a function to get the current serializer/reducer * a function to set the serializer/reducer * an abstract base class to assist others

[issue28053] parameterize what serialization is used in multiprocessing

Changes by Davin Potts : -- components: +Library (Lib) ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue28053] parameterize what serialization is used in multiprocessing

New submission from Davin Potts: Currently multiprocessing uses the pickle module for its serialization of objects to be communicated between processes. Specifically v2 of the pickle protocols is now exclusively used to provide maximum compatibility, motivated by the desire for multiple versi