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 musically_ut
Recipients musically_ut
Date 2013-10-23.11:22:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The JSON parser currently throws exceptions which contain information about where the error happened but this information is encoded in a string and not available to the programmer. This leads to issues like this:

Would it be a problem if the errors thrown were specialized exceptions, e.g. JSONParsingError, which has ValueError as a base class with these details (line number, char number, etc.) exposed as public members? The changes required seem to be limited to changing and the related documentation.
Date User Action Args
2013-10-23 11:22:14musically_utsetrecipients: + musically_ut
2013-10-23 11:22:14musically_utsetmessageid: <>
2013-10-23 11:22:14musically_utlinkissue19361 messages
2013-10-23 11:22:13musically_utcreate