Recent changes to bugs

Doesn't handle unicode input

Steve Rogerson — Tue, 30 May 2017 12:03:22 -0000

If the json "string" is unicode the parser fails.
Changing :

        if type(key) is not types.StringType:

to
if type(key) is not types.StringType and type(key) is not types.UnicodeType:

at line 213 sorts this out

Spaces and Tabs

Stephen Pike — Sat, 07 Feb 2009 13:34:26 -0000

The package works beautifully but the readability is undermined by the mixture of spaces and tabs in the file...

http://www.python.org/dev/peps/pep-0008/

Please fix!
:-D

Tuple used as dict key

Anonymous — Tue, 22 Jul 2008 19:51:45 -0000

See for yourself

>>> import pyjson
>>> pyjson.write({(1,2) : "a"})
'{[1,2]:"a"}'
>>> pyjson.read('{[1,2]:"a"}')

Traceback (most recent call last):
File "<pyshell#128>", line 1, in <module>
pyjson.read('{[1,2]:"a"}')
File "C:\Python25\lib\pyjson.py", line 309, in read
return JsonReader().read(s)
File "C:\Python25\lib\pyjson.py", line 53, in read
result = self._read()
File "C:\Python25\lib\pyjson.py", line 62, in _read
return self._readObject()
File "C:\Python25\lib\pyjson.py", line 214, in _readObject
raise ReadException, "Not a valid JSON object key (should be a string): %s" % key
ReadException: Not a valid JSON object key (should be a string): [1, 2]

So it does accept tuples as keys whilst encoding, but won't decode them anymore.

Error on empty array

Anonymous — Wed, 20 Dec 2006 15:28:52 -0000

On parsing JSON with an empty array with a newline between the opening and closing bracket the parser throws an error:

json.ReadException: Input is not valid JSON: '[\n]
'

input can be as simple as this:

[
]

Strange problem

Peter "mash" Morgan — Sun, 17 Dec 2006 04:10:43 -0000

I'm already using the PHP json_encode function to encode data for some Ajax apps, and the pygtk app I'm working on is an extension of this.

However I get an error with the string below. The crux is that if the "data=" is removed from the front it works in python. However with the "data=" there is fails in Python but works on browsers?

So which is incorrect, the browsers interperation or the json.py ??

Apart from that it works great. It would also ne nice to have a couple of examples on the website and am prepared to do that.

Regards
Pete

-- Dont like this ---
in php >> echo 'data='.json_encode($users);

data={"3":{"user":"Beth Morgan","status":"out","date_in":"2006-11-05 10:00:00","dat":"2006-11-05","tim":"10:00:00"}}

-- This is ok ---
echo json_encode($users);

{"3":{"user":"Beth Morgan","status":"out","date_in":"2006-11-05 10:00:00","dat":"2006-11-05","tim":"10:00:00"}}

Doesn't handle numbers with exponentials correctly.

Anonymous — Sat, 07 Oct 2006 08:21:15 -0000

Doesn't handle numbesr of the form 3.746484E7 correctly
(throws an exception).

This is easy to fix, just change line 112 to:
while peek is not None and (peek.isdigit() or
peek == "." or peek == "E")

this isn't robust, will allow through 3.444EEE2, so
obviously not great. But it'll get the library working
again.

minjson.py backslashed quotes fix

Dan Helfman — Mon, 09 Jan 2006 19:32:58 -0000

Calling _getStringState() to count quotes around a
potentially DoS-causing mathematical expression
generally works just fine. However, if there happen to
be backslashed quotes within the string being checked,
then those quotes are counted within _getStringState(),
even though they are backslashed and shouldn't be
counted. The fix is to remove backslashed quotes from
the string being tested from _sanityCheckMath() before
trying to count quotes. Attached is a patch to fix this.

write should raise an exception on invalid dict keys.

Anonymous — Sun, 25 Sep 2005 13:41:09 -0000

json.read("{1:'value'}'") #will raise an exception on
an invalid integer key.

json.write({1:'value'}) #Will not raise an exception on
the integer key.

Martijn.

tests fail when run as python -O

Anonymous — Sun, 18 Sep 2005 14:59:02 -0000

json.py relies on side affects in assert statements
which are compiled out when python is run with
optimization (-O).

to reproduce: python -O jsontests.py

also, could you have the archive unpack to a directory
that contains the same name as the archive (ie.
json-py-3_4) instead of hosing the current working
directory. it would also be nice if json-py used
distutils (http://docs.python.org/dist/dist.html).

finally, you may want to consider listing json-py in
the cheeseshop (http://cheeseshop.python.org) as it is
becoming the standard place for python software.

thanks,
wes

Comments not allowed before array/object closing

Koen van de Sande — Mon, 08 Aug 2005 20:50:13 -0000

Two more test cases which are valid JSON but not parsed
properly. Note that the empty array bug does not make
the second test case useful just yet (but it fails on
my own fixed version).

json.read('[{} /*Comment*/]')

json.read('{"test": [] /*Comment*/}')