After reading that ticket, I'm not sure what Alex and I are disagreeing on. I was suggesting using django.utils.simplejson internally until it's removed, so that at least people could be consistent with django itself. That way, DjangoJSONEncoder would be a simplejson.JSONEncoder (if simplejson is installed) until we remove the shim.
I agree w/ deprecating utils.simplejson, and I agree that leaky shims are a fundamental problem, but it does seem to me that the state of play could be better by not using simplejson and json both in the same codebase. DjangoJSONEncoder(json.JSONEncoder) but django.utils.simplejson is simplejson if it's available. Anyway, since we've already deprecated utils.simplejson, since we've already done the damage here, and since doing a release to fix this is probably not going to help that many people (they've either already fixed their backwards-incompat or aren't planning on going to 1.5 any time soon)... maybe I agree we should leave it alone. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
