Open ni-tterry opened 7 years ago
Ok, this is interesting. I expect that what's happening is that the breakpoint somehow makes the object unserializable -- just as a guess. ppft
uses dill.source
for serialization (not pickling, but extracting the relevant source code from the object, and passing that).
Could you post a small bit of code that produces the issue? This way, I can try it. Also versions of the codes you are using is helpful information.
Hi, I'm having the same issue. I've had a previous problem with parallel pool where I was getting different results for my parallel code than I was getting for single processing code (my code is a Class where use a univariate spline interpolation to transform/smooth a noisey data set). Anwyay, I tried to debug in PyCharms and got the below output after my breakpoints for ParallelPool. I'm not sure if this is the reason as to why I'm getting the different outputs for parallel and single processing, as I have not been able to find one, but maybe this has something to do with it. Nonetheless I'm a bit lost and have found little on the web that explains this Communication pipe read error. Any help or advice as how to I should proceed would be greatly appreciated. Here is my PyCharm's debugger output,
Connected to pydev debugger (build 172.3317.103)
Traceback (most recent call last):
File "C:\Users\lloyd.smith\PyCharm Community Edition 2017.2\helpers\pydev\pydevd.py", line 1596, in
Process finished with exit code 1
I think the issue is with ppft and pycharm. I changed my code so it used ProcessPool from pathos.multiprocessing and the 'communication pipe read erro'r stopped occurring. After making this change, I'm now getting a cPickle.PicklingError. Fortunately, I switched over to a Mac Os operating system and the code runs just fine with no errors.
Hey folks! Thanks for your work on this extensive multiprocessing fork.
I am looking at pathos to circumvent some pickling problems using traditional multiprocessing. However, it seems like I can't attach a debugger anytime after a ParallelPool is instantiated:
This happens any time I hit a breakpoint after the ParallelPool is created. It does not happen with pathos.multiprocessing.Pool.