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
Since the deepcopy is going to happen anyway, I think it should be done under SchemaMeta.__new__. This way one could have access to the final fields from the schema class without the need for instantiation.
The text was updated successfully, but these errors were encountered:
I'm not 100% sure what the actual ramifications for doing this are - the Schema is an instance of SchemaMeta and can have instance variables set on it that are not accessible from the instance at all (well, from my testing and prodding) which makes serialization more complicated.
I think it's an interesting quirk (feature?) of the type system, but I'm not sure what the practical applications are.
Closing this for now, as this has gone stale and we don't have immediate plans to implement this. Feel free to re-open if there's more to discuss here.
Since the deepcopy is going to happen anyway, I think it should be done under
SchemaMeta.__new__
. This way one could have access to the final fields from the schema class without the need for instantiation.The text was updated successfully, but these errors were encountered: