Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
0.6.0
-
None
Description
In the first iteration of the Python serialization code, we used global variables to store the custom serialization and deserialization callback functions. This global state is undesirable because if the user wants to use different serialization callbacks with different types registered, they need to remember resetting the state. As Wes suggested, a good way to address this is by introducing a SerializationContext that has the callbacks and gets passed around.