New submission from Benedikt Sauer:
When raising an exception that is unpicklable in a worker process. This used to
be the case for all exceptions that have a non-trivial constructor but this was
fixed by http://bugs.python.org/issue1692335.
I now have the concrete problem with cx_Oracle in which the error type
cx_Oracle._Error doesn't define tp_new which results in a
UnpicklingError: NEWOBJ class argument has NULL tp_new
I have already reported this fact at
https://bitbucket.org/anthony_tuininga/cx_oracle/issues/23.
However, I think that the worker thread should either be able to recover from
this (which should be quite easy) or, at the very least, fail cleanly.
Currently, when this condition is triggered the worker processes are not killed
alongside the parent.
There is an existing report and a patch in the backports project:
https://github.com/agronholm/pythonfutures/issues/30#issuecomment-132576545
----------
messages: 248878
nosy: filmor
priority: normal
severity: normal
status: open
title: Raising an exception that is unable to be unpickled causes hang in
ProcessPoolExecutor
versions: Python 3.3
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue24900>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
