Option 2 looks best to me. There's no reason for us to ship JSON any more, but we should still guide people through the transition process.
Yours, Russ Magee %-) On 30/03/2012, at 7:07 AM, Łukasz Rekucki wrote: > Alex's comment on ticket #18013 reminded me of this. Is there any > reason not to get rid of the Django's version of simplejson now that > Python 2.6 always has the json module? > > I see three options here: > > 1) Remove Django's copy and only leave the simplejson/json fallback. > 2) Above, plus deprecate "django.utils.simplejson" in 1.5 and remove it 1.6 > 3) Replace the code with anyjson, so it does something useful: > http://pypi.python.org/pypi/anyjson > > What do you think ? > > -- > Łukasz Rekucki > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected]. > 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. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. 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.
