stefanofontanelli/ColanderAlchemy — pull request #25 by offlinehacker (2013-05-19 01:47:44+00:00)
Title: Default strategy for column and relationship include should be changed.

Now it's really weird. For the table in first depth, if no includes are specified, all columns and relationships are included, but for all children tables only columns are included. I think behavior must be consistent and that relationships should always be included, or you can still specify in excludes to exclude them. The following two lines are unecessary and are causing problems in my case:

if includes is None and excludes is None:
includes = [p.key for p in inspect(class_).column_attrs]