Jared Deckard

That error occurs during schema construction, not the dump operation. The move to be more strict about field names came about to prevent typos from running without warning and silently...

Inheritance is another good use case where `Meta` is likely to only need a few attributes. I was initially imagining spreading the parent meta manually like `@meta(..., **vars(ParentSchema.Meta))`, but that...

I ended up having to subclass the schema to get `SchemaMeta.__new__` to rebuild `opts` from `Meta`. I am going to test drive this utility for a little while. ```py def...

> I ended up having to subclass the schema to get `SchemaMeta.__new__` to rebuild `opts` from `Meta`. This also rebuilds `_declared_fields` with the new meta options.

I published a module for this functionality. I think this should just be a community library for now. Once I cover it with tests I will add it to the...

Changing `AttributeError` to other exception classes does not reproduce the issue. `getattr` uses the default when an `AttributeError` is raised in a property method. ```py class Data: @property def name(self):...

> I would like to create a deserialisation only schema Can you expand on what exactly you think should happen when the schema is serialized? Setting everything to load_only will...

In my IDE the aliases lose their type and docstring. The autocomplete plugin doesn't know how to infer this information, because it doesn't try to do any runtime evaluation. We...

They are referring to the fact that there is no hook between `load(in_data, many)` and `@validates` in the processing pipeline. https://marshmallow.readthedocs.io/en/stable/extending.html#pre-post-processor-invocation-order You can write validators that modify the data before...

I think users are mostly expected to build `only` on the fly as needed. If your schema is usually filtered by default you could build up the schema with inheritance....