Make fields deserialization more strict ?

Working with the library, it appears to me that the deserialization module has a lack of strictness from my point of view:

class DocSchema(Schema):
    str = fields.String()
   bool = fields.Boolean()

# Ok, None is not implicitly acceptable
DocSchema().load({'str': None, 'bool': None})
# UnmarshalResult(data={}, errors={'str': ['Field may not be null.'], 'bool': ['Field may not be null.']})

# But it's not the case for numbers
DocSchema().load({'str': 42, 'bool': 42})
# UnmarshalResult(data={'str': '42', 'bool': True}, errors={})

# Or for any complex structure (list, dict)
DocSchema().load({'str': {}, 'bool': {}})
# UnmarshalResult(data={'str': '{}', 'bool': False}, errors={})

Is there a way to enforce real strict validation ? Passing a dict as argument of a string field without getting any error sounds like a silent fail for me…

[stefanoborini]

We are facing a similar lack of strictness with a String field that, when presented with a tuple, converts it into a string and stores it as such. We would like to guarantee that no repr() conversion takes place, and only legitimate strings go in the field.

[sloria]

Good catch @density . Will fix shortly.