This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry
Recipients barry
Date 2014-01-31.10:08:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391162931.99.0.108127691347.issue20453@psf.upfronthosting.co.za>
In-reply-to
Content
Run the attached file under Python 3.3 and you get:

No JSON object could be decoded

Run the same file under Python 3.4 and you get:

Expecting value: line 1 column 1 (char 0)

So a couple of things:

Since the error message changed, it makes it difficult to test in doctest and other text-based matches.  I'm also not sure the new message is "better".  Objectively speaking, probably both error messages are useful (i.e. that no json object was found, and where the problem was found).  I think the second message by itself is pretty mysterious.

I want to make sure the change was deliberate.  I couldn't find anything in Misc/NEWS which might not be entirely unexpected since specific error messages aren't generally a part of the guaranteed API.  Perhaps at the least, if the change was deliberate, let's document it in Misc/NEWS.
History
Date User Action Args
2014-01-31 10:08:52barrysetrecipients: + barry
2014-01-31 10:08:51barrysetmessageid: <1391162931.99.0.108127691347.issue20453@psf.upfronthosting.co.za>
2014-01-31 10:08:51barrylinkissue20453 messages
2014-01-31 10:08:51barrycreate