On 30 March 2012 13:04, Alex Ogier <[email protected]> wrote: > At the same time, I want to reiterate my support for option #1: not > deprecating the > module and leaving the shim in for the foreseeable future. If simplejson is > available on the system, and particularly if it has been compiled with C > extensions, then there is a significant performance gain to be had, so why > not continue to take advantage of that in all the places that django > serializes to json?
I agree this is a valid concern and I think it should be mentioned in release notes. If you want more performance, then option #3 (anyjson) would actually be better, but I don't think it should be Django's concern to choose the best JSON package for you (we don't do that for XML). Instead, imho, Django should provide an ability to pass a custom JSON encode/decoder to all APIs that require it, so you can decide about it at the project level. -- Ł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.
