Mailing List Archive

[issue9400] multiprocessing.pool.AsyncResult.get() messes up exceptions
Daniel Blanchard <dan.blanchard@gmail.com> added the comment:

The patch appears to fix the issue, so is there any chance of this actually getting accepted this time? It seems bizarre that such a simple bug that has been on the books for almost two years now can't get a patch accepted.

----------

_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue9400>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
[issue9400] multiprocessing.pool.AsyncResult.get() messes up exceptions [ In reply to ]
Changes by Antoine Pitrou <pitrou@free.fr>:


----------
nosy: +sbt

_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue9400>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
[issue9400] multiprocessing.pool.AsyncResult.get() messes up exceptions [ In reply to ]
Richard Oudkerk <shibturn@gmail.com> added the comment:

There are plenty of other "bad" exception classes apart from CalledProcessError, including TimeoutExpired in the same file. In fact I suspect this is true of the majority of the exception classes in the stdlib which override __init__. So I am not sure how much good it would do to fix just one example.

Python 3.x's Pool wraps bad exception instances in a MaybeEncodingError class which at least lets you see a stringification of the original exception. I am not sure whether you would want to see a backport of this. Even though 2.7 is in bug fix mode, I think a backport would still be appropriate since it stops a pickling error from killing a worker process, causing a hang.

----------

_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue9400>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
[issue9400] multiprocessing.pool.AsyncResult.get() messes up exceptions [ In reply to ]
Roundup Robot <devnull@psf.upfronthosting.co.za> added the comment:

New changeset 26bbff4562a7 by Richard Oudkerk in branch '2.7':
Issue #9400: Partial backport of fix for #9244
http://hg.python.org/cpython/rev/26bbff4562a7

----------
nosy: +python-dev

_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue9400>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
[issue9400] multiprocessing.pool.AsyncResult.get() messes up exceptions [ In reply to ]
Richard Oudkerk <shibturn@gmail.com> added the comment:

I have backported the fix for issue #9244 to 2.7. This should fix the hang and produce a traceback containing a representation of the original error.

----------

_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue9400>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com