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 Uri Okrent
Recipients Uri Okrent, berker.peksag, loewis, serhiy.storchaka
Date 2016-06-09.18:40:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465497611.71.0.738148076685.issue27281@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not pickling/unpickling it directly, I'm using multiprocessing to handle queries to my server in worker processes which is using pickle to propagate exceptions raised in the worker to the parent.

I could instead raise a different exception and wrap it in a Fault later (which is what I ended up doing to avoid the issue), but it seems like a case of "to-may-to" vs. "to-mah-to".  Either way an Exception should be able to be propagated up to the parent in multiprocessing, whether it's my own or Fault.
History
Date User Action Args
2016-06-09 18:40:11Uri Okrentsetrecipients: + Uri Okrent, loewis, berker.peksag, serhiy.storchaka
2016-06-09 18:40:11Uri Okrentsetmessageid: <1465497611.71.0.738148076685.issue27281@psf.upfronthosting.co.za>
2016-06-09 18:40:11Uri Okrentlinkissue27281 messages
2016-06-09 18:40:11Uri Okrentcreate