Comment 14 for bug 834361

I reviewed all upstream changes in simplejson between 2.0.9 (the version in Lucid) and 2.1.1 for potentially breaking changes:

- there was a new feature, object_pairs_hook, that added a fair amount of code. This caused a regression that was caught before release: http://code.google.com/p/simplejson/source/detail?r=195
- http://code.google.com/p/simplejson/source/detail?r=181 causes a new exception JSONDecodeError to be raised on a decoding error rather than ValueError. That could in theory have a compatibility impact, but it's unlikely because JSONDecodeError inherits from ValueError. So to be broken, a client would need to be depending on the exact class ValueError being raised; 'except ValueError' would continue to work.

I didn't see any other changes that might be risky for compatibility.