On Nov 30, 9:51 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > * Django 1.1: JSON serialization looks for system json/simplejson > first, fall back to django.utils.simplejson if not found and warn > with PendingDeprecationWarning whenever django.utils.simplejson is > used. > > * Django 1.2: Continue looking for system json/simplejson and falling > back, but the PendingDeprecationWarning becomes a > DeprecationWarning. > > * Django 1.3: django.utils.simplejson is removed, and attempting to > use it simply gets you an ImportError. Use of JSON serialization > will require separate installation of simplejson, or Python 2.6 with > the json module.
I think that if you just shift this timeline so that the PendingDeprecationWarning starts on Django 1.2 and that it gets dropped at Django 1.4, then it fits in with the proposed timeline for Python deprecation. If that Python deprecation timeline is followed, then at Django 1.4, Python 2.6 will be assumed and thus the json module could be assumed as well. -Eric Florenzano --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
