Referring to a Schema by its name as string is a common use case, a feature that a user may have to use before he gets much experience, so having this working by default, and without scattering the code with Meta classes, is nice. Therefore I'd say let's keep registration at True by default.
This memory usage issue is a pitfall for users with more advanced needs. Hopefully, we can assume
those user should have read a bit of documentation and an explicit warning pointing to this feature should be enough.
This is totally arguable and I don't have a strong opinion either way.
Referring to a Schema by its name as string is a common use case, a feature that a user may have to use before he gets much experience, so having this working by default, and without scattering the code with Meta classes, is nice. Therefore I'd say let's keep this at False.
Purpose
Implement a way to bypass marshmallow's internal class registry when it isn't necessary in order to optimize memory usage.
Proposed API
The text was updated successfully, but these errors were encountered: