[issue34034] Python 3.7.0 multiprocessing forkserver ForkingPickler behaviour change

Antoine Pitrou added the comment: No problem! I'm going to close this issue as I don't think there's anything we can do here. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker

[issue34034] Python 3.7.0 multiprocessing forkserver ForkingPickler behaviour change

Santiago Hernandez added the comment: Thanks, I get it now, I hadn't seen that the pickling of the workers was Processes pickling. Yeah, I was not doing this anywhere else, it seems like slipped through once. But it called my attention that it used to work and now it doesn't. On Tue, Jul 3, 20

[issue34034] Python 3.7.0 multiprocessing forkserver ForkingPickler behaviour change

Antoine Pitrou added the comment: It could be many different things. The bottom line here, though, is that the Process class is not designed to be picklable (how would it work?), which is probably why you're seeing this. -- nosy: +pitrou ___ Pyth

[issue34034] Python 3.7.0 multiprocessing forkserver ForkingPickler behaviour change

New submission from Santiago Hernandez : Hi, I am splitting some processing among different processes with the forkserver start method using multiprocessing. In python 3.4 to 3.6 this worked fine. In python 3.7.0 it's breaking with the following Traceback: ``` File "/data/venvs/py37/Python