I think a better approach would be to have django.utils.simplejson as a sort of alias package (which is easy using Python's introspection). What would happen is this:
A user imports either django.utils.simplejson, or something from inside it. We look for the 'json' package on the path (Python 2.6 stdlib). If found, use this. We look for the 'simplejson' package on the path. If found, and with a more recent version than the bundled version, use this. Otherwise, we have a bundled version which gets used. That way, we can be relatively sure of the stability of the simplejson we're shipping, but if a user wants the bleeding edge library then they can just keep doing things the same way but install simplejson (or use Python 2.6). Don't forget that the bug-fixing of simplejson will probably grind to a near-halt now it's part of the stdlib, only being updated every release of Python. This means that we can bundle a recent version and be relatively secure that no major changes will be made. I don't think this is nearly as big a problem as it's made out to be, and I for one like the security of knowing I can always just import django.utils.simplejson as a "guaranteed to be there" JSON library. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
