Jérôme Lafréchoux

> BTW, I suppose we had the symmetric issue with default before that change. It would be interesting to check. Confirmed. This code, before #756 (I actually tried on 2.x-line),...

Due to the former (MA2) behaviour, when people use `{}` as `nested_field.missing` value, they may not mean "`{}`" but "this is an empty value, please give me the default load...

I like the idea. I always thought marshmallow lacked this feature. The recurring questions about polymorphism show there is a need. Although this does not mean oneofschema would answer the...

Notes: - I renamed a few local variables in `Schema` methods to be more explicit: `data_key` instead of `field_name`. We might want to rename `field_name` attribute of `_call_and_store` because it...

I performed a quick test on apispec codebase to see how things could be simplified there and the result is a bit disappointing. apispec operates on schema instances or classes,...

I'm not sure this is safe to change this in marshmallow 3 but we could think of it for v4, along with the thoughts about setting/getting field attributes.

Thanks for the contribution and sorry for about the delay. I have no objection to this, even if [the SO answer](https://stackoverflow.com/a/21872376) underlines the fact that in practice there are currently...

> yes, this regex will affect the domain validations as well since email and domain validation shares the same regex. I had a quick look and I thought it uses...

Dumping unknown data would be complicated because objects may have attributes you don't want to dump. It only makes sense for dicts or objects where the content to be dumped...

Would it replace or update an existing (inherited) `Meta` class? Updating would allow stacking, although I don't really see the use case for stacking.