[Python-Dev] Bug in json (the format and the module) (original) (raw)

Bob Ippolito bob at redivi.com
Tue May 17 20🔞15 CEST 2011

• Previous message: [Python-Dev] Bug in json (the format and the module)
• Next message: [Python-Dev] Bug in json (the format and the module)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

By default the json module already escapes anything outside of 7-bit ASCII, so unless you're using ensure_ascii=False then this is a non-issue.

I implemented a workaround for ensure_ascii=False in simplejson here, it would be pretty trivial to add this feature to the json module as well: https://github.com/simplejson/simplejson/commit/4989e693bab39b1ce5cf6fc0b21dbacd108c312c

On Tue, May 17, 2011 at 11:40 AM, Jeremy Dunck <jdunck at gmail.com> wrote:

This blog post describes a bug in a common usage pattern of JSON:

http://timelessrepo.com/json-isnt-a-javascript-subset That is, there are some characters which are legal in JSON serializations, but not in JavaScript strings. This works OK for JSON parsers, but a common use case of JSON is JSONP, where the result of a request is presumed to be executable javascript: