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 asksol
Recipients asksol, eliquious, flox, jnoller, macfreek, max, vstinner
Date 2012-09-12.11:54:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347450910.08.0.989786570384.issue9592@psf.upfronthosting.co.za>
In-reply-to
Content
I vote to close too as it's very hard to fix in a clean way.

A big problem though is that there is a standard for defining exceptions, that also ensures that the exception is pickleable (always call Exception.__init__ with original args), that is not documented (http://docs.python.org/tutorial/errors.html#user-defined-exceptions).

Celery has an elaborate mechanism to rewrite unpickleable exceptions, but it's a massive workaround just to keep the workers running, and shouldn't be part of the stdlib.  It would help if the Python documentation mentioned this though.

Related: http://docs.celeryproject.org/en/latest/userguide/tasks.html#creating-pickleable-exceptions
History
Date User Action Args
2012-09-12 11:55:10asksolsetrecipients: + asksol, vstinner, macfreek, jnoller, flox, max, eliquious
2012-09-12 11:55:10asksolsetmessageid: <1347450910.08.0.989786570384.issue9592@psf.upfronthosting.co.za>
2012-09-12 11:54:49asksollinkissue9592 messages
2012-09-12 11:54:48asksolcreate