Steven Loria

Oh good catch. So the current validation appears to be correct then. I think we can close this

closed by #2244

@vgavro I think this is a fair use case. I anticipate that users will typically want to deserialize to timezone-aware datetimes, so the API should make this simple. I haven't...

I would gladly review and merge a PR adding a `Timestamp` field.

Ah, yes, I see your @vgavro . Yes, I suppose it could be a new datetime format. I'm fine with that.

Thanks for the detailed report. Seems like there's two main asks here: 1. Fields should accept data that is in the deserialized type, e.g. `datetime -load-> datetime` 2. `load` and...

> (1) is all we need. We build dicts of data (json, essentially) and want to pass them to Schema.validate. Oh ok. Seems reasonable. For now, can you workaround this...

@lafrech Wdyt about changing this in marshmallow?

I don't think we should add a flag for it--unnecessary API surface. I also don't see much downside.

@deckar01 I'm good with that proposal. What do you think of the proposal above to modify fields to accept data in their deserialized type?