Non ValidationError Exceptions still get silently put into errors list about marshmallow

[sloria]

The current behavior is for Fields to capture any uncaught exceptions (unless they are wrapped with ForcedError) and store them in the errors dictionary.

The idea was to save the field's from having to do much exception handling and instead allow the abstract Field class catch all the errors.

I realize now that this leads to undesired behavior when an exception is raised during deserialization that is unrelated to data formatting or type validation.

I am in the process of refactoring the fields so that each field is responsible for deciding which errors get stored in the errors dictionary.

Thanks for reporting this.