Paul Eipper

Definitely! The docs are outdated from before 2.0 release. Pull requests for docs are welcome too.

Hi, schematics has this feature, for example to select only filled fields on serialization: ```python from schematics.models import Model from schematics.types import StringType from schematics.common import NONEMPTY class User(Model): name...

Most of these flags are optional to keep compatibility with old behaviour. I think @bintoro proposed to change that in the future to make the defaults more explicit. Docs still...

HashType is used as an abstract type, but I agree it should have some more obvious way to signal that.

With 2.0.0 now on PyPI, and update to the docs would be very welcome: https://pypi.python.org/pypi/schematics/2.0.0

Needs to be refactored according to suggestions before pulling it in.

I agree on the correctness point, I even started to model the algorithm in TLA+ formal language, to try to pin down the core (see my doc-math branch here https://github.com/nKey/schematics/tree/doc-math/docs/math...

Loops don't tend to explode the stack as recursion does. On Monday, 9 November 2015, Kirk Strauser [email protected] wrote: > Ooh, 👍🏻x10 for #351 https://github.com/schematics/schematics/pull/351 > and #355 https://github.com/schematics/schematics/pull/355! >...

Yes, get rid on `Model._initial` and split instance `raw_data` from validated `data`. My patch only works against 0.9x tho.

Re `_initial`: If the user needs the original data, they can always just add a property dynamically or subclass. Don't see a reason to complicate the API for that. Re...