Re: Customizable Serialization Idea -GSoC
Thanks for the advice! Of course I will apply in these year and do the
home work. If some one has any other resource I it can be usefull ,
plese post it. So If I have some advances I will share it with all!
2010/2/23 Russell Keith-Magee <freakboy3...@gmail.com>:
> On Tue, Feb 23, 2010 at 1:26 PM, Jesus Mager <fon...@gmail.com> wrote:
>> Hi all!
>>
>> My name is Jesus Mager, and I'm student at the National Autonomous
>> University of Mexico.I am interested in in taking part of Google
>> Summer of Code for the diango project.
>> The Customizable Serialization sound a good idea. Django have actually
>> a really fine system, so we can handle xml, json and yaml
>> serialization that are hard-coded in different files.
>> If I don't miss some thing, Django should now have a class, maybe
>> using the same serializers class that handle the different formats.
>>
>> from django.core import serializers
>> data = serializers.serialize("xml", SomeModel.objects.all())
>>
>> Where "xml" indicates that serializer will use xml_serializer.py. To
>> customiz these, the serialize object should use some methods that help
>> the I/O of the different formats, and the whole proceeding can be
>> written in a XML file. If customize class is initiated with the
>> argument "format" then __init__ will load the respective xml file (if
>> any) that indicates how to handle the serialization and
>> deserialization. Its just a idea. I hope we can discuss it.
>
> I'm certainly interested in seeing someone take a swing at this for the GSoC.
>
> As a bit of background reading - there were a couple of students who
> submitted proposals about customizable serialization for last year's
> GSoC. None of these proposals were successful, but the discussions
> will hopefully be helpful in shaping your own proposal.
>
> [1]
> http://groups.google.com/group/django-developers/browse_thread/thread/f6a3166ab46e28af
> [2]
> http://groups.google.com/group/django-developers/browse_thread/thread/145e2b7ec53a1996
>
> If you're still interested, the next step is to digest all this, and
> come up with a concrete API proposal. If you're intending to
> participate in the GSoC, it's better to start early; a mature proposal
> has a much better chance of getting accepted. The last two GSoC
> projects that I have mentored started their design processes *long*
> before the official start of the GSoC.
>
>> I know that google don't have yet made the mentor organizations
>> selection but I hope Django will be again a mentor organization
>> because It is a really cool software.
>
> I'm sure we'll be applying again, and I can't think of any reason we
> wouldn't be successful.
>
> Yours,
> Russ Magee %-)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@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.
>
>
--
Jesus Mager
[www.h1n1-al.blogspot.com]
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@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.
Customizable Serialization Idea -GSoC
Hi all!
My name is Jesus Mager, and I'm student at the National Autonomous
University of Mexico.I am interested in in taking part of Google
Summer of Code for the diango project.
The Customizable Serialization sound a good idea. Django have actually
a really fine system, so we can handle xml, json and yaml
serialization that are hard-coded in different files.
If I don't miss some thing, Django should now have a class, maybe
using the same serializers class that handle the different formats.
from django.core import serializers
data = serializers.serialize("xml", SomeModel.objects.all())
Where "xml" indicates that serializer will use xml_serializer.py. To
customiz these, the serialize object should use some methods that help
the I/O of the different formats, and the whole proceeding can be
written in a XML file. If customize class is initiated with the
argument "format" then __init__ will load the respective xml file (if
any) that indicates how to handle the serialization and
deserialization. Its just a idea. I hope we can discuss it.
I know that google don't have yet made the mentor organizations
selection but I hope Django will be again a mentor organization
because It is a really cool software.
A last issue. Is these the correct list, or should I use the gsoc special list?
Cheers!
--
Jesus Mager
[www.h1n1-al.blogspot.com]
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@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.
Re: Porting Django to Python 3
Hi all! I'm CS student at the National Autonomous University of Mexico, and I'm very interested to porting Django to Python 3 too. I hope the efforts porting Django will be public on a svn branch, so I can also collaborate. And of course, if a core developer can guide us, it will be much better. 2010/1/8 Russell Keith-Magee <freakboy3...@gmail.com>: > On Sat, Jan 9, 2010 at 2:25 AM, Dave <weber...@gmail.com> wrote: >> Hello everyone, >> >> My name is Dave Weber, and I'm a student at the University of Toronto, >> studying Computer Science. For one of our undergraduate courses led by >> Greg Wilson (http://www.cs.utoronto.ca/~gvwilson/), myself and a group >> of 10 other computer science students will be trying to port Django to >> Python 3. >> >> Until the end of January, we'll be studying the existing Django code >> in order to gain an understanding of how the program works. We'll be >> doing this primarily through architecture documentation and >> performance profiling. In early February we plan on beginning work on >> the port. >> >> A few of us have experience working with Django, and by the end of >> January we should have a much better understanding of it. I've been in >> touch with Jacob Kaplan-Moss, who pointed me to this group, and he >> also provided me with links about contributing to the Django project >> and Martin van Lowis' port. >> >> We don't really have any specific questions right now as we're pretty >> unfamiliar with most of the project at this point in time. However, we >> are very eager to learn as much as we can, so if you have any advice, >> warnings, or anything at all to say to us, please feel free! We'd like >> to hear from all of you as much as possible. > > Hi Dave, > > Sounds like an interesting project! > > My best piece of advice would be to learn to love the test suite. > Django's test suite may take a long time to run, but it is quite > comprehensive, and has enabled us to complete several large internal > refactoring projects with a minimum of impact on the general user > community. > > My other advice would be to get involved in the community. Don't just > treat your Python 3 port as "your CS project", independent of the rest > of the world. For example, if your porting efforts discovers a section > of code that isn't tested (or tested well), or you discover a simple > fix that will boost performance, don't be a stranger - submit a patch > and help us make Django better. > > This even extends to documentation - if your porting efforts generate > architecture documentation that might be useful to the general > community, we'd love to have that contributed back to the community. > > Best of luck with your project. I can't wait to see what you come up with :-) > > Yours, > Russ Magee %-) > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@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. > > > > -- Jesus Mager [www.h1n1-al.blogspot.com] -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
