-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pathos still giving pickle error #262
Comments
What version of |
I am also getting a can't pickle an object error using pathos ProcessPool . But my example is pretty complex, so it is very hard to create something smaller and reproducible. I am using pathos 0.3.0 and multiprocess 0.70.14 The failure I am having is in trying to pickle an class from the module pylibczirw I have included the traceback below if that is any help. I do notice from the traceback that the root exception is coming from line 388 in _dill and that looks like some sort of attempt to try using StockPIckler.save(), so it would appear that dill does use pickle in some situations. File "C:\Users\Doug\AppData\Local\pypoetry\Cache\virtualenvs\ultistacker-ai-wqxucbEU-py3.9\lib\site-packages\dill_dill.py", line 388, in save and if you look at the code in _dill.py near line 388 (last line in the snippet below) you can see:
Here is a more complete traceback: File "C:\dev\ultistacker.ai\ultistacker\Stacker.py", line 923, in process_tiles Thank you for your help with this! |
yes, that's true. What I said was @dougwood: so this seems like a different issue than the OP, so probably belongs in it's own issue. |
Hi,
I switches to Pathos.multiprocessing instead of multiprocessing but still getting a similar error with pickle dump.
Here is simplifed version of the code
I want to pass a tuple to function every time and leave other argument default which load the files and mask. But still getting the same error which appears in multiprocesisng library.
This the error trace.
Anyone faced a similar issue or solved it?
Thanks
The text was updated successfully, but these errors were encountered: