> 1) It's almost illegible. Between your mail client's munging of line > wrapping, and the completely unreadable code samples, it's very > difficult to tell if you have presented a good idea.
Pardon the format. I actually auto-wrapped the text with vim and copy pasted at the first time. Realizing the result is ugly, I actually deleted it from the thread (using the google group web) and reposted without extra formatting. I was going to apologize for the duplication but didn't want to further spam everyone on this list. I believe what you read is the first copy, and the 2nd would be better. > 2) You haven't done the one thing that the Django GSoC wiki recommends > -- provide, as a proof of your concept, an expression of Django's own > serializers using your proposed serialization syntax. > > If you'd done any research on the topic, you'd find that I've raised > the second point every single time this topic is proposed -- in fact, > there's a currently active django-dev discussion with another student > proposing a serialization project. I regret that the unfortunate format stopped you from reading through my proposal, but my code example merely presented a case where the "extra" customization is provided: excluding fields, renaming key names, serializing nested objects. If none of above needs exist, then the user *don't* need to write anything. A default configuration would be used. And that, I assumed from the beginning, would be the current format the serializers use. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
