Any reason to continue using simplejson over the included json in Python 2.7?

Question

The reason in the past used to be that simplejson was way faster than the included json but now they are pretty similar in speed. Do I get any benefits sticking with simplejson anymore or should I switch all my code over to the included json now?

possible duplicate of json and simplejson module differences in Python — JBernardo
– JBernardo, Commented Feb 15, 2012 at 22:05

Andrew Clark · Accepted Answer · 2012-02-15 22:21:04Z

2

One practical difference is that when loading JSON strings, the json module will always return a Python unicode object, but simplejson will return a str (byte string) unless the JSON string contains Unicode code points:

>>> json.loads('"test"')
u'test'
>>> simplejson.loads('"test"')
'test'
>>> simplejson.loads('"\\u1000"')
u'\u1000'

So, you may want to stick with simplejson if you have poorly written code that can't handle unicode returns when loading JSON (I say poorly written because simplejson.loads() will return unicode depending on the JSON string).

answered Feb 15, 2012 at 22:21

Andrew Clark

210k36 gold badges285 silver badges310 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Qurben · Accepted Answer · 2012-02-15 21:55:56Z

-1

Google appengine doesn't support json. On top of that simplejson is more updated than json

answered Feb 15, 2012 at 21:55

Qurben

1,3161 gold badge10 silver badges21 bronze badges

Collectives™ on Stack Overflow

Any reason to continue using simplejson over the included json in Python 2.7?

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related