This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Uri Okrent, berker.peksag, loewis, serhiy.storchaka
Date 2016-06-09.19:08:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465499322.57.0.545652256062.issue27281@psf.upfronthosting.co.za>
In-reply-to
Content
This looks reasonable.

But since Fault never was unpickleable, this issue is in gray zone between bug fixing and adding new feature. The latter can be done only in new Python version. I hesitate with classification of this issue.

There are a lot of other exceptions that can't be unpickled (including xmlrpc.client.ProtocolError). This may be a part of larger issue.

As for the patch itself, it solves the issue. But faultCode and faultString are saved twice (this is not a large problem for multiprocessing). Test should test pickling with all possible protocols (see how other pickle tests are written).
History
Date User Action Args
2016-06-09 19:08:42serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, berker.peksag, Uri Okrent
2016-06-09 19:08:42serhiy.storchakasetmessageid: <1465499322.57.0.545652256062.issue27281@psf.upfronthosting.co.za>
2016-06-09 19:08:42serhiy.storchakalinkissue27281 messages
2016-06-09 19:08:42serhiy.storchakacreate