Thanks Piotr,
> But when serializing also Field is saved with data so it's not so clean.
I'm not sure whether it's an issue or not. As with Django's form fields,
the fields are copied off of base_fields, so saving state
isn't necessarily a problem. I'd agree that it's possibly not the cleanes
W dniu 31.08.2012 10:25, Tom Christie pisze:
> I personally think that Forms are already the place that should
handle (de)serialisation. They already serialise to HTML: why should
they not be able to serialise to other stream types?
Conceptually I agree. As it happens django-serializers is pe
> Do you know Colander?
I do now. Thanks, that's very similar, and looks well done.
> I personally think that Forms are already the place that should handle
(de)serialisation. They already serialise to HTML: why should they not be
able to serialise to other stream types?
Conceptually I agree.
Not sure that I phrased the last bit right: I think my repose framework is
a step in the right direction, but even so I think it probably doesn't do
things the right way.
Matt.
On Wednesday, August 29, 2012 2:57:35 PM UTC+9:30, schinckel wrote:
>
> Hi Tom,
>
> I've knocked around ideas of my o
Hi Tom,
I've knocked around ideas of my own (internally, and on #django) related to
serialisation: it's something I've had lots to think about, since until
recently, most of my django work was in JSON apis.
I personally think that Forms are already the place that should handle
(de)serialisatio
Do you know Colander?
https://github.com/Pylons/colander
- D
2012/8/28 Tom Christie
> Hi all,
>
> During Piotr's GSOC addressing customizable serialization I've been
> continued to work on my own implementation.
> I've now got what feels to me to be a natural conclusion of the design,
> whi
