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 r.david.murray
Recipients Luka.Rahne, eric.araujo, ezio.melotti, maker, r.david.murray
Date 2012-10-04.14:45:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
So you would see a copy of the string being decoded in the error message?  That string might be very long, and would be of doubtful utility.  What I had in mind was at least printing the character position of the parse failure.  That may also be of limited utility, though, since in many cases the parse failure will happen at the end of the string.  This is a problem for all parsers, and the solution is often non-trivial, depending on the parser.  

Someone who wants to see this happen will need to look at the parser and see what information it has at the point of parse failure that might be useful and practical to expose.
Date User Action Args
2012-10-04 14:45:30r.david.murraysetrecipients: + r.david.murray, ezio.melotti, eric.araujo, maker, Luka.Rahne
2012-10-04 14:45:30r.david.murraysetmessageid: <>
2012-10-04 14:45:30r.david.murraylinkissue16009 messages
2012-10-04 14:45:30r.david.murraycreate