Fails where embedded copy in python 2.6 works about simplejson HOT 3 CLOSED

I also filed https://code.djangoproject.com/ticket/16850 on the Django side in case Django is improperly using the simplejson interface.

from simplejson.

It looks like the problem here is that Django expects that decimal objects will get converted to string (by its default method) instead of a JSON number. This change was made for usability reasons in 2.2.0, most people want decimals to get encoded as numbers even though there's a possible loss of precision if decoded on the other end without the right options. This behavior can be turned back off with use_decimal=False on encode. The version embedded in Django also supports this option (default False rather than True), so it would be compatible with whichever version of dump/dumps ends up getting used.

from simplejson.

I'm going to close this for now, it's technically a feature and not a bug. I would prefer if Django explicitly asked for the behavior they are expecting.

Re-open if the Django folks would rather simplejson be stuck with its 2.2.0 defaults for now, and I'll revert the behavior and release 2.3.0. Not my preference to do this, since having use_decimal=True on encoding by default is what users have expected for a long time.

from simplejson.