Refactor Field.serialize()

[deckar01]

#788 was caused by confusion between Field.serialize() and Field._serialize().

Field.serialize() plucks a value out of a schema level object and passes it on to Field._serialize(). Field.serialize() is only used in Marshaller.serialize().

I propose moving Field.serialize() to Marshaller.serialize_field() and Field.deserialize() to Marshaller.deserialize_field() to avoid this confusion.

[sloria]

Seems like a sensible change. I'll mark it for 3.0, since it would be a backwards-incompatible change, though I'm not sure this needs to be a hard blocker for 3.0 final.

[lafrech]

@deckar01 we may postpone this, unless you think it is an easy job.

[sloria]

I still think this would be a good change. I don't think it's a must-have for 4.0, but would be nice. @deckar01 would you be interested in implementing this?

[sloria]

this is part of what you're proposing in #1046, right? should we close this one and continue discussion in that issue?

[lafrech]

It is related, indeed. Could be a first step. Or we may want to deal with the whole thing in one go. No problem with closing this in favor of #1046.