-
Notifications
You must be signed in to change notification settings - Fork 51
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
Raising an exception that is unable to be unpickled causes hang in ProcessPoolExecutor #30
Comments
I would need a test for this fix too. |
When possible, you can workaround this by allowing this exception to have zero arguments (by default parameters). At least that fixed it for me until the patch is through. |
The patch also contains a test, if I'm not mistaken ... |
Hm, yes it does! How did I miss that. |
I'm surprised that there is no fix for this in upstream code. Is it not a problem on Python 3? |
It sure is. Frankly, I wasn't aware that this one here is the backports project, I'll file a bug for Python 3.3. |
I'll wait until upstream developers comment on it until applying any fix. |
This is the upstream bug: http://bugs.python.org/issue24900 |
Is this still relevant? If so, how do I reproduce it? |
Original issue reported on code.google.com by
[email protected]
on 30 Sep 2014 at 2:23Attachments:
The text was updated successfully, but these errors were encountered: