[issue17906] JSON should accept lone surrogates

Serhiy Storchaka added the comment: Updated patch submitted in issue11489. -- status: open -> closed ___ Python tracker ___ ___ Python

[issue17906] JSON should accept lone surrogates

Serhiy Storchaka added the comment: I forgot about issue11489. After reclassification this issue is it's duplicate. -- resolution: -> duplicate superseder: -> json.dumps not parsable by json.loads (on Linux only) ___ Python tracker

[issue17906] JSON should accept lone surrogates

Bob Ippolito added the comment: The patch that I wrote for simplejson is here (it differs a bit from serhiy's patch): https://github.com/simplejson/simplejson/commit/35816bfe2d0ddeb5ddcc68239683cbb35b7e3ff2 I discovered another bug along the way in the pure-Python scanstring, int(s, 16) will

[issue17906] JSON should accept lone surrogates

Changes by Serhiy Storchaka : Added file: http://bugs.python.org/file30131/json_decode_lone_surrogates-2.7.patch ___ Python tracker ___ ___ P

[issue17906] JSON should accept lone surrogates

Serhiy Storchaka added the comment: After investigating the problem deeper, I see that new parameter is not needed. RFC 4627 does not make exceptions for the range 0xD800-0xDFFF, and the decoder must accept lone surrogates, both escaped and unescaped. Non-BMP characters may be represented as e