You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
import msgspec
class TaggedException(msgspec.Struct, Exception, tag=True): pass
However, this reliably segfaults Python (CPython 3.12.5, msgspec 0.18.6).
I presume there is some kind of incompatibility between the C-level layout of Struct objects and Exception objects? Are there any good alternatives for encoding exception objects? (which seems super usefil when implementing APIs) Maybe this cannot be fixed. But maybe it should at least throw an error instead of crashing the interpreter?
Thanks for opening this. In prior versions msgspec had a check preventing mixing Struct classes with other builtin types - this check was broken on Python 3.12 but is now fixed in #745. The above example now errors nicely rather than segfaulting. If you want to encode exceptions I recommend following a pattern like the one @provinzkraut outlined above rather than defining an Exception type that is also a Struct.
Activity
provinzkraut commentedon Aug 28, 2024
I usually do something like this:
and then use this
enc_hookwhenever I'm encoding stuff that might contain one of those exceptions.jcrist commentedon Oct 14, 2024
Thanks for opening this. In prior versions msgspec had a check preventing mixing
Structclasses with other builtin types - this check was broken on Python 3.12 but is now fixed in #745. The above example now errors nicely rather than segfaulting. If you want to encode exceptions I recommend following a pattern like the one @provinzkraut outlined above rather than defining anExceptiontype that is also aStruct.