[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
resolution:  -> fixed
stage:  -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Roundup Robot]

Roundup Robot added the comment:

New changeset 02d186e3af09 by Serhiy Storchaka in branch '2.7':
Fixed JSON tests on wide build when ran from *.pyc files (issue #11489).
http://hg.python.org/cpython/rev/02d186e3af09

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Arfrever Frehtes Taifersar Arahesis]

Arfrever Frehtes Taifersar Arahesis added the comment:

test_json_surrogates.patch fixes these tests.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Thank you Arfrever. Does this patch fix the test?

--
Added file: http://bugs.python.org/file32922/test_json_surrogates.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Arfrever Frehtes Taifersar Arahesis]

Arfrever Frehtes Taifersar Arahesis added the comment:

... when code is loaded from .pyc files (i.e. when `make test` runs tests the 
second time).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Arfrever Frehtes Taifersar Arahesis]

Arfrever Frehtes Taifersar Arahesis added the comment:

New tests fail on 2.7 branch, at least with Python configured with 
--enable-unicode=ucs4 (which is default in Gentoo):

==
FAIL: test_surrogates (json.tests.test_scanstring.TestCScanstring)
--
Traceback (most recent call last):
  File 
"/var/tmp/portage/dev-lang/python-2.7.7_pre20131201/work/python-2.7.7_pre20131201/Lib/json/tests/test_scanstring.py",
 line 107, in test_surrogates
assertScan(u'"z\\ud834\udd20x12345"', u'z\ud834\udd20x12345')
  File 
"/var/tmp/portage/dev-lang/python-2.7.7_pre20131201/work/python-2.7.7_pre20131201/Lib/json/tests/test_scanstring.py",
 line 97, in assertScan
(expect, len(given)))
AssertionError: Tuples differ: (u'z\ud834\udd20x12345', 16) != 
(u'z\U0001d120x12345', 16)

First differing element 0:
z\ud834\udd20x12345
z\U0001d120x12345

- (u'z\ud834\udd20x12345', 16)
+ (u'z\U0001d120x12345', 16)

==
FAIL: test_surrogates (json.tests.test_scanstring.TestPyScanstring)
--
Traceback (most recent call last):
  File 
"/var/tmp/portage/dev-lang/python-2.7.7_pre20131201/work/python-2.7.7_pre20131201/Lib/json/tests/test_scanstring.py",
 line 107, in test_surrogates
assertScan(u'"z\\ud834\udd20x12345"', u'z\ud834\udd20x12345')
  File 
"/var/tmp/portage/dev-lang/python-2.7.7_pre20131201/work/python-2.7.7_pre20131201/Lib/json/tests/test_scanstring.py",
 line 97, in assertScan
(expect, len(given)))
AssertionError: Tuples differ: (u'z\ud834\udd20x12345', 16) != 
(u'z\U0001d120x12345', 16)

First differing element 0:
z\ud834\udd20x12345
z\U0001d120x12345

- (u'z\ud834\udd20x12345', 16)
+ (u'z\U0001d120x12345', 16)

--

--
nosy: +Arfrever
resolution: fixed -> 
stage: committed/rejected -> 
status: closed -> open

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
resolution:  -> fixed
stage: patch review -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Roundup Robot]

Roundup Robot added the comment:

New changeset c85305a54e6d by Serhiy Storchaka in branch '2.7':
Issue #11489: JSON decoder now accepts lone surrogates.
http://hg.python.org/cpython/rev/c85305a54e6d

New changeset 8abbdbe86c01 by Serhiy Storchaka in branch '3.3':
Issue #11489: JSON decoder now accepts lone surrogates.
http://hg.python.org/cpython/rev/8abbdbe86c01

New changeset 5f7326ed850f by Serhiy Storchaka in branch 'default':
Issue #11489: JSON decoder now accepts lone surrogates.
http://hg.python.org/cpython/rev/5f7326ed850f

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

I there are no objections I'll commit this patch soon.

--
assignee:  -> serhiy.storchaka
Added file: 
http://bugs.python.org/file32718/json_decode_lone_surrogates_3-3.4.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Taras Prokopenko]

Taras Prokopenko added the comment:

You should use ensure_ascii=False option to json.dumps, ie

import json
unicode_bytes = '\xed\xa8\x80'
unicode_string = unicode_bytes.decode("utf8")
json_encoded = json.dumps(unicode_string, ensure_ascii=False)

json.loads(json_encoded),unicode_string
(u'\uda00', u'\uda00')
cmp(json.loads(json_encoded),unicode_string)
0

--
nosy: +Taras.Prokopenko

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Raymond Hettinger]

Changes by Raymond Hettinger :


--
assignee: rhettinger -> 

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


--
components: +Extension Modules
stage: needs patch -> patch review

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Serhiy Storchaka]

Changes by Serhiy Storchaka :


Added file: 
http://bugs.python.org/file30235/json_decode_lone_surrogates_2-2.7.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

Here are updated patches from issue17906. Updated tests, fixed a bug reported 
by Bob Ippolito in msg188857 and fixed inconsistency noted by Ezio Melotti on 
Rietveld (Python implementation now raises same exception as C implementation 
on illegal hexadecimal escape).

--
Added file: http://bugs.python.org/file30234/json_decode_lone_surrogates_2.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

I forgot about this issue and open a new issue17906. There is a patch for it. 
Simplejson has accepted it in 
https://github.com/simplejson/simplejson/issues/62.

RFC 4627 does not make exceptions for the range 0xD800-0xDFFF (unescaped = 
%x20-21 / %x23-5B / %x5D-10), and the decoder must accept lone surrogates, 
both escaped and unescaped. Non-BMP characters may be represented as escaped 
surrogate pair, so escaped surrogate pair may be decoded as non-BMP character, 
while unescaped surrogate pair shouldn't.

--
nosy: +bob.ippolito
versions: +Python 3.3, Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

About patch.  I think "with" is unnecessary here. One-line 
self.assertRaises(UnicodeEncodeError, self.dumps, ch) looks better for me.

--
stage:  -> needs patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Ezio Melotti]

Ezio Melotti added the comment:

Attached failing test.

--
keywords: +patch
Added file: http://bugs.python.org/file27369/issue11489.diff

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Serhiy Storchaka]

Serhiy Storchaka added the comment:

> It's Unicode that considers unpaired surrogates invalid, not UTF-8 by itself.

It's UTF-8 too. See RFC 3629:

   The definition of UTF-8 prohibits encoding character numbers between
   U+D800 and U+DFFF, which are reserved for use with the UTF-16
   encoding form (as surrogate pairs) and do not directly represent
   characters.  When encoding in UTF-8 from UTF-16 data, it is necessary
   to first decode the UTF-16 data to obtain character numbers, which
   are then encoded in UTF-8 as described above.

--
nosy: +storchaka

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Petri Lehtinen]

Petri Lehtinen added the comment:

Bear in mind that Douglas Crockford thinks a JSON document is valid even if it 
contains unpaired surrogates:

http://tech.groups.yahoo.com/group/json/message/1603
http://tech.groups.yahoo.com/group/json/message/1583

It's Unicode that considers unpaired surrogates invalid, not UTF-8 by itself.

--
nosy: +petri.lehtinen

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Raymond Hettinger]

Changes by Raymond Hettinger :


--
assignee:  -> rhettinger
priority: high -> normal

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +pitrou, tchrist
versions:  -Python 2.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Ezio Melotti]

Ezio Melotti  added the comment:

RFC 4627 doesn't say much about lone surrogates:
   A string is a sequence of zero or more Unicode characters [UNICODE].
   [...]

   All Unicode characters may be placed within the
   quotation marks except for the characters that must be escaped:
   quotation mark, reverse solidus, and the control characters (U+
   through U+001F).

   Any character may be escaped.  If the character is in the Basic
   Multilingual Plane (U+ through U+), then it may be
   represented as a six-character sequence: a reverse solidus, followed
   by the lowercase letter u, followed by four hexadecimal digits that
   encode the character's code point.  The hexadecimal letters A though
   F can be upper or lowercase.  So, for example, a string containing
   only a single reverse solidus character may be represented as
   "\u005C".
   [...]

   To escape an extended character that is not in the Basic Multilingual
   Plane, the character is represented as a twelve-character sequence,
   encoding the UTF-16 surrogate pair.  So, for example, a string
   containing only the G clef character (U+1D11E) may be represented as
   "\uD834\uDD1E".


Raymond> JSON is UTF-8 by definition and it is a useful feature that invalid 
UTF-8 won't load.

Even if the input strings are not encodable in UTF-8 because they contain lone 
surrogates, they can still be converted to an \u escape, and the resulting 
JSON document will be valid UTF-8.
AFAIK json always uses \u, so it doesn't produce invalid UTF-8 documents.

While decoding, both json.loads('"\xed\xa0\x80"') and json.loads('"\ud800"') 
result in u'\ud800', but the first is not a valid UTF-8 document because it 
contains an invalid UTF-8 byte sequence that represent a lone surrogate, 
whereas the second one contains only ASCII bytes and it's therefore valid.
Python 2.7 should probably reject '"\xed\xa0\x80"', but since its UTF-8 codec 
is somewhat permissive already, I'm not sure it makes much sense changing the 
behavior now.  Python 3 doesn't have this problem because it works only with 
unicode strings, so you can't pass invalid UTF-8 byte sequences.

OTOH the Unicode standard says that lone surrogates shouldn't be passed around, 
so we might decide to replace them with the replacement char U+FFFD, raise an 
error, or even provide a way to decide what should be done with them (something 
like the errors argument of codecs).

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[STINNER Victor]

STINNER Victor  added the comment:

print(repr(json.loads(json.dumps({u"my_key": u'\uda00'}))['my_key'])):
 - displays u'\uda00' in Python 2.7, 3.2 and 3.3
 - raises a ValueError('Invalid \u escape: ...') on loads() in Python 2.6
 - raises a ValueError('Unpaired high surrogate: ...') on loads() in Python 3.1

json version changed in Python 2.7: see the issue #4136.

See also this important change in simplejson:
http://code.google.com/p/simplejson/source/detail?r=113

We only fix security bugs in Python 2.6, not bugs. I don't think that this 
issue is a security bug in Python 2.6.

We might change Python 3.1 behaviour.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Ezio Melotti]

Changes by Ezio Melotti :


--
nosy: +ezio.melotti

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Ezio Melotti]

Changes by Ezio Melotti :


Removed file: http://bugs.python.org/file21135/unnamed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Brian]

Brian  added the comment:

On Mon, Mar 14, 2011 at 4:09 PM, Raymond Hettinger
wrote:

>
> Raymond Hettinger  added the comment:
>
> > We seem to be in the worst of both worlds right now
> > as I've generated and stored a lot of json that can
> > not be read back in
>
> This is unfortunate.  The dumps() should have never worked in the first
> place.
>
> I don't think that loads() should be changed to accommodate the dumps()
> error though.  JSON is UTF-8 by definition and it is a useful feature that
> invalid UTF-8 won't load.
>

I may be wrong but it appeared that json actually encoded the data as the
string "u\da00" ie (6-bytes) which is slightly different than the encoding
of the utf-8 encoding of the json itself.  Not sure if this is relevant but
it seems less severe than actually invalid utf-8 coding in the bytes.

Unfortunately I don't believe this does anything on python 2.x as only
python 3.x encode/decode flags this as invalid.

> --
> nosy: +rhettinger
> priority: normal -> high
>
> ___
> Python tracker 
> 
> ___
>

--
nosy: +merrellb
Added file: http://bugs.python.org/file21135/unnamed

___
Python tracker 

___On Mon, Mar 14, 2011 at 4:09 PM, Raymond Hettinger rep...@bugs.python.org> 
wrote:


Raymond Hettinger rhettin...@users.sourceforge.net>
 added the comment:

> We seem to be in the worst of both worlds right now
> as I've generated and stored a lot of json that can
> not be read back in

This is unfortunate.  The dumps() should have never worked in the first 
place.

I don't think that loads() should be changed to accommodate the dumps() 
error though.  JSON is UTF-8 by definition and it is a useful feature that 
invalid UTF-8 won't load. I may be wrong 
but it appeared that json actually encoded the data as the string 
"u\da00" ie (6-bytes) which is slightly different than the encoding 
of the utf-8 encoding of the json itself.  Not sure if this is relevant but it 
seems less severe than actually invalid utf-8 coding in the bytes.

 

To fix the data you've already created (one that other compliant JSON 
readers wouldn't be able to parse), I think you need to repreprocess those 
file to make them valid:

   bs.decode('utf-8', 
errors='ignore').encode('utf-8')Unfortunately
 I don't believe this does anything on python 2.x as only python 3.x 
encode/decode flags this as invalid.

 
--
nosy: +rhettinger
priority: normal -> high

___
Python tracker rep...@bugs.python.org>
http://bugs.python.org/issue11489>
___

___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Raymond Hettinger]

Raymond Hettinger  added the comment:

> We seem to be in the worst of both worlds right now 
> as I've generated and stored a lot of json that can 
> not be read back in

This is unfortunate.  The dumps() should have never worked in the first place.

I don't think that loads() should be changed to accommodate the dumps() error 
though.  JSON is UTF-8 by definition and it is a useful feature that invalid 
UTF-8 won't load.

To fix the data you've already created (one that other compliant JSON readers 
wouldn't be able to parse), I think you need to repreprocess those file to make 
them valid:

   bs.decode('utf-8', errors='ignore').encode('utf-8')

Then we need to fix dumps so that it doesn't silently create invalid JSON.

> This on the other hand should probably be 
> fixed by either rejecting lone surrogates 
> in json.dumps or accepting them in json.loads or both.

Rejection is the right way to go.  For the most part,
it is never helpful to create invalid JSON files that
other readers can't and shouldn't read.

--
nosy: +rhettinger
priority: normal -> high

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Brian Merrell]

Brian Merrell  added the comment:

>I am not sure this should be fixed in 2.x. Lone surrogates seem to >round-trip 
>just fine in 2.x and there likely to be existing code that >relies on this.

I generally agree but am then at a loss as to how to detect and deal with lone 
surrogates(eg "ignore", "replace", etc) in 2.x when interacting with 
services/libraries (such as Python's own json.loads) that take a stricter view.

>>  Shouldn't anything generated by json.dumps be parsed by json.loads?

>This on the other hand should probably be fixed by either rejecting >lone 
>surrogates in json.dumps or accepting them in json.loads or both.  >The last 
>alternative would be consistent with the common wisdom of >being conservative 
>in what you produce but liberal in what you accept.

We seem to be in the worst of both worlds right now as I've generated and 
stored a lot of json that can not be read back in.  Could the JSON library 
simply leverage Python's Unicode interpreter instead of performing its own 
validation?  We could pass it "ignore", "replace", etc.  Regardless, I think we 
certainly need to remove the strict JSON loads() validation especially when it 
isn't enforced by dumps().

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Alexander Belopolsky]

Alexander Belopolsky  added the comment:

> It appears this is an invalid unicode character.
> Shouldn't this be caught by decode("utf8")

It should and it is in Python 3.x:

>>> b'\xed\xa8\x80'.decode("utf8")
Traceback (most recent call last):
  File "", line 1, in 
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 0-1: invalid 
continuation byte

Python 2.7 behavior seems to be a bug.

>>> '\xed\xa8\x80'.decode("utf8")
u'\uda00'

Note also the following difference:

In 3.x:

>>> b'\xed\xa8\x80'.decode("utf8", 'replace')
'��'

In 2.7:

>>> '\xed\xa8\x80'.decode("utf8", 'replace')
u'\uda00'

I am not sure this should be fixed in 2.x. Lone surrogates seem to round-trip 
just fine in 2.x and there likely to be existing code that relies on this.

>  Shouldn't anything generated by json.dumps be parsed by json.loads?

This on the other hand should probably be fixed by either rejecting lone 
surrogates in json.dumps or accepting them in json.loads or both.  The last 
alternative would be consistent with the common wisdom of being conservative in 
what you produce but liberal in what you accept.

--
nosy: +belopolsky, haypo
versions: +Python 2.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue11489] json.dumps not parsable by json.loads (on Linux only)

[Brian Merrell]

New submission from Brian Merrell :

The following works on Win7x64 Python 2.6.5 and breaks on Ubuntu 
10.04x64-2.6.5.  This raises three issues:

1)  Shouldn't anything generated by json.dumps be parsed by json.loads?
2)  It appears this is an invalid unicode character.  Shouldn't this be caught 
by decode("utf8")
3)  Why does Windows raise no issue with this and Linux does?

import json
unicode_bytes = '\xed\xa8\x80'
unicode_string = unicode_bytes.decode("utf8")
json_encoded = json.dumps("my_key":unicode_string)
json.loads(json_encoded)

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.6/json/__init__.py", line 307, in loads
return _default_decoder.decode(s)
  File "/usr/lib/python2.6/json/decoder.py", line 319, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.6/json/decoder.py", line 336, in raw_decode
obj, end = self._scanner.iterscan(s, **kw).next()
  File "/usr/lib/python2.6/json/scanner.py", line 55, in iterscan
rval, next_pos = action(m, context)
  File "/usr/lib/python2.6/json/decoder.py", line 183, in JSONObject
value, end = iterscan(s, idx=end, context=context).next()
  File "/usr/lib/python2.6/json/scanner.py", line 55, in iterscan
rval, next_pos = action(m, context)
  File "/usr/lib/python2.6/json/decoder.py", line 155, in JSONString
return scanstring(match.string, match.end(), encoding, strict)
ValueError: Invalid \u escape: line 1 column 14 (char 14)

--
components: Library (Lib), Unicode, Windows
messages: 130779
nosy: Brian.Merrell
priority: normal
severity: normal
status: open
title: json.dumps not parsable by json.loads (on Linux only)
type: behavior
versions: Python 2.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com