It seems like everyone besides me agrees on option #2 so I implemented it in #18023 <https://code.djangoproject.com/ticket/18023> ( https://github.com/ogier/django/compare/remove-simplejson ). 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?
Best, Alex Ogier On Fri, Mar 30, 2012 at 4:13 AM, Florian Apolloner <f.apollo...@gmail.com>wrote: > Hi, > > I am for number 2 too, but don't forget that's deprecation in 1.5 and 1.6 > and removal in 1.7 > > Cheers, > Florian > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/mzYEOlCKfHkJ. > > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > 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 django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
