On Tue, Feb 16, 2010 at 1:43 PM, orokusaki <flashdesign...@gmail.com> wrote: > Thank you Karen. I've been hushed so many times about this, yet there > seems to be a growing concern (hence the search traffic, and number of > results) about why you can't naturally do this with Django's built-in > serializer.
I have no problem if you want to advocate for this idea, but let's keep the hyperbole under control. I see absolutely no evidence for your claim for a "growing concern". * The ticket in question is 9 months old; and has 4 comments on it, two of which are procedural "closed, wontfix". Compare and contrast with #7052 or #2070 to see what an *active* ticket looks like. * The google search you present as evidence of "growing concern" has plenty of false positives, including: "cache_page takes a single argument: the cache timeout, in seconds. .... The cache module, django.core.cache, has a cache object that's automatically created ..." "I have a single file and need to serialize multiple objects of the same class when ever a new object is created. I can't store them in arrays as I need to ..." * Even if you accept the google search results as meaningful, 5800 documents is hardly a crushing number. For comparison "Django serialize multiple objects" returns 4910 results. If you want to make an argument for allowing single-object serialization, I'm happy to entertain that discussion. However, appeal to popularity shouldn't form part of that discussion. Doing things to be popular didn't work in high school, and I don't see why it should start working with Django. We (the core) will make a judgement based on the merits of a proposal, not based on some desire to do the "popular" thing (although there's no reason the two shouldn't coincide). It's also worth keeping in mind that this feature would be a feature addition, and therefore will need to wait until Django 1.3 at this point. I would also point out that personally, I have a very high internal resistance to tinkering with the current serialization framework, in view of the fact that what is needed is a wholesale reworking of the framework to allow for better customization. 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.
