Opened 10 years ago
#230 new enhancement
when a failure is not serializable, try to indicate which exception type was responsible
Reported by: | davidsarah | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | undecided |
Component: | banana | Version: | 0.7.0 |
Keywords: | serialization Violation | Cc: |
Description
A common reason to get a foolscap.tokens.Violation
is that some exception type transitively references an unserializable object. However the traceback doesn't provide any information about where to start looking, i.e. which exception type. In some cases, even without trying to fix the unserializability, just knowing the exception type would be a sufficient clue to the cause of the original error.
Note: See
TracTickets for help on using
tickets.