-
-
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
Exception handling with ParallelPool #228
Comments
Sorry for the slow reply. I'm seeing the same issue as you... Results from the interpreter:
Results are no different when running from a file.
I also see that the errors are raised, but are not caught. Note that I'm not seeing the same issue you are with the string being printed oddly. Let me know what OS and versions of the code you are using. Hmm. If I remember correctly |
I tried several things.
Not very sure what's causing it but this might be relevant to the OS. |
is there a reason you are using |
0.2.8 is the version that I used to use when I saw the issue with the binary symbols. Here is what I just tried:
Below is what got written into
|
Hmm. That's helpful... and so weird. Thanks I'll see if I can reproduce it. |
Thanks for making this great library! I have a question regarding to how exception handling could be done with
ParallelPool
. UsingProcessPool
, errors can be caught as normal. However withParallelPool
, the error couldn't be caught likeProcessPool
see below. It seems like the error of all three worker processes are printed out to stderr directly, but none of then are caught.We also noticed that some binary strings are printed out with the error messages. There is a "%" symbol in the end of the example below, but in real life, we got something like this:
I'm wondering if the
ParallelPool
has its own way of error handling and please point me to it if it is already documented!The text was updated successfully, but these errors were encountered: