Jérôme Lafréchoux

Great. Is there the same kind of gap between `Nested(many)` and `List(Nested)` when loading?

I still need to get my head around this. I suppose `Tuple` would be impacted as well. In your example, I don't understand why you use `List` in the first...

I don't remember whether it was meant to work in marshmallow 2 or whether it just happened to work. I guess it works if you make that method a property.

I understand making the method a property may not be an option. I can't tell whether this is a regression that should be documented or if it was not designed...

Thanks for reporting and sorry about the delay. Indeed there is an inconsistency. See related discussion in #1617 and an implementation proposal for marshmallow 4 in #1826. What would you...

I don't know the original intent for this feature either. I've never used it. To me, the point is to allow modifying the behaviour at runtime. Your sample code uses...

This would avoid issues with users sharing schema instances between requests (#1825) and it would solve nested schema issues (#1617). I like the idea of a global context variable common...

This is achieved in #2017 and #2044 (released in 3.18.0).

See #546. Looks like there are (were ?) several competing implementations. Let's make sure we pick the right one if we go on with this.

Looks like none is packaged on Debian. Since we don't use all features of an ordered set, and since performance doesn't matter that much on schema creation, I'm wondering if...