Hi Piotr, Thank you so much for your efforts over the summer.
I'd also like to apologise for my lack of communication; I certainly haven't been a model mentor over the course of the program. Although we may not have achieved all the goals we set out to achieve at the start of the program, I don't think it's been a complete loss -- we've certainly thrashed out some interesting ideas, and between your work and Tom's, I'm sure we can salvage something that the community can make use of. Now that the program has finished, If you have any feedback about what we could do differently next year, I'd love to hear it. Obviously, we'd like every SoC student to be a complete success, so if there's anything the Django team could do to improve the chances of success for next year's program, I'd like to be able to learn from the mistakes of this year. Yours, Russ Magee %-) On Thu, Aug 23, 2012 at 8:14 AM, Piotr Grabowski <[email protected]> wrote: > Hi, > > Google Sumer of Code is almost ended. I was working on customizable > serialization. This project was a lot harder than I expected, and sadly in > my opinion I failed to do it right. I want to apologize for that and > especially for my poor communication with this group and my mentor. I want > to improve it after midterm evaluation but it was only worse. > > I don't think my project is all wrong but there is a lot things that are > different from how I planned. How it looks like (I wrote more in > documentation) > There is Serializer class that is made of two classes: NativeSerializer and > FormatSerializer. > NativeSerializer is for serialization and deserialization python objects > from/to native python datatypes > FormatSerializer is for serialization and deserialization python native > datatypes to/from some format (xml, json, yaml) > > I want NativeSerializer to be fully independent from FormatSerializer (and > vice versa) but this isn't possible. Either NativeSerializer must return > some additional data or FormatSerializer must give NativeSerializer some > context. For exemple in xml all python native datatypes must be serialized > to string before serializing to xml. Some custom model fields can have more > sophisticated way to serialize to sting than unicode() so > `field.value_to_string` must be called and `field` are only accessible in > NativeSerializer object. So either NativeSerializer will return also `field` > or FormatSerializer will inform NativeSerializer that it handles only text > data. > > Backward compatible dumpdata is almost working. Only few tests are not > passed, but I am not sure why. > > Nested serialization of fk and m2m related fields which was main > functionality of this project is working but not well tested. There are some > issues especially with xml. I must write new xml format because old wont > work with nested serialization. > > I didn't do any performance tests. Running full test suite take 40 seconds > more with my serialization (about 1500s at all) if I remember correctly. > > I will try to complete this project so it will be at least bug free and > usable. If someone was interested in using nested serialization there is > other great project: https://github.com/tomchristie/django-serializers > > Code: https://github.com/grapo/django/tree/soc2012-serialization > Documentation: https://gist.github.com/3085250 > > > -- > Piotr Grabowski > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
