Tim Tisdall

one minor correction: `schema_type` is expected to be a callable with no arguments and `typ` is expected to just be a property. So aliasing would be something like `schema_type =...

> Finally the pattern of doing self.**dict**.update(kw) in SchemaNode.**init** is pretty terrible as it turns all of these very real errors into silent no-ops. This pattern should be reconsidered when...

... only issue with the above suggestion is it destroys the symmetry that someone was going for here: http://docs.pylonsproject.org/projects/colander/en/latest/basics.html?highlight=schema_type#subclassing-schemanode However, that example is already broken as passing in `schema_type` as...

@mmerickel - Do you have any suggestions for dealing with the above doc example? Should we perhaps allow `schema_type` in the constructor as an alias for `typ`?

does any of #237 help?

Yeah, that does seem like a bug. I'm curious if any of the existing tests fail after fixing this. It may have been missed because 'drop' wasn't well documented for...

I'd probably call it a "limitation". The `unflatten` method expects a flattened mapping. If you pass it something that's only partially flattened, it'd be nice if if it retained the...

I like the base idea, but there seems to be a new Bitcoin fork every day now so I think this might be difficult to make as a centralized CSV....

Okay, it seems like there's an expectation that every element is expected to be there. I think it should use the default value if the value is absent.

@rnevet , I haven't looked at the config code, but is it possible to throw an error if there's a configuration setting that's unrecognized to avoid the issue with a...