On 7/12/07, James Bennett <[EMAIL PROTECTED]> wrote: > The other modules you mention are optional to a certain extent (don't > technically need flup to do Django-as-WSGI, can use Django without a > database or with your choice of DB adapter), but simplejson is > absolutely required for the serialization system (and hence test > fixtures and initial data loading) to work. Similarly, Django's > internal dispatch system relies on pydispatcher and will not function > without it, so pydisptatcher is bundled directly in Django.
I'm probably missing something stupid here, but this doesn't seem accurate to me. It looks as though the JSON serializer is actually the only one that uses simplejson, not the whole serialization framework. It seems like the JSON serializer could use the same method as it already does for YAML, checking to see if the proper dependency is there, ignoring it if it's not. Admittedly, JSON is quite likely going to be the most common serializer used, but it just doesn't seem like JSON should be considered a minimum requirement for the serialization framework. Of course, on that note, I could also (somewhat feebly) argue that it seems odd to put the serializers in django.core instead of django.contrib. They're a very handy feature, yes, but I don't see anything else in the core that actually relies on it. Keep in mind, though, I don't use the serializers and I don't really know all that much about their history, so I'm probably missing some really obvious things that completely contradict everything I'm saying. -Gul --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
