[issue20453] json.load() error message changed in 3.4

Berker Peksag added the comment: 3.4 is in security-fix-only mode and 3.5+ has better error messages thanks to JSONDecodeError (07af9847dbec). Closing this as 'out of date'. -- nosy: +berker.peksag resolution: -> out of date stage: -> resolved status: open -> closed _

[issue20453] json.load() error message changed in 3.4

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue20453] json.load() error message changed in 3.4

Serhiy Storchaka added the comment: In issue19361 I suggest to change error messages even more and drop end position from "Extra data" error message. -- ___ Python tracker ___ _

[issue20453] json.load() error message changed in 3.4

Antoine Pitrou added the comment: > To me new error messages look more informative and more correct. Yes, I agree with you. -- ___ Python tracker ___ ___

[issue20453] json.load() error message changed in 3.4

Serhiy Storchaka added the comment: "No JSON object could be decoded, expecting value" is too expensive and second part of this message just repeat first part. The message can be shortened to "No JSON object could be decoded". But this is not fully correct. JSON term "object" corresponds to Py

[issue20453] json.load() error message changed in 3.4

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue20453] json.load() error message changed in 3.4

Barry A. Warsaw added the comment: On Jan 31, 2014, at 04:23 PM, R. David Murray wrote: >If backward compatibility is the concern, I'd think you'd just want to >restore that one message. Yeah. I think the tests are a little more difficult to adjust in that case, and of course, if we do change

[issue20453] json.load() error message changed in 3.4

R. David Murray added the comment: If backward compatibility is the concern, I'd think you'd just want to restore that one message. -- ___ Python tracker ___ ___

[issue20453] json.load() error message changed in 3.4

Barry A. Warsaw added the comment: So, here's a patch that should work. One thing I'm not positive about is that this is a more expansive change then just merging the two messages in the one case in the original description. But it probably makes sense to be consistent. Or should we try for

[issue20453] json.load() error message changed in 3.4

R. David Murray added the comment: It seems to me that it should indeed have been that way. I thought the referenced issue was *adding* the location information to the existing error messages. -- nosy: +r.david.murray ___ Python tracker

[issue20453] json.load() error message changed in 3.4

Barry A. Warsaw added the comment: What do you think of combining the error messages, e.g. No JSON object could be decoded, expecting value: line 1 column 1 (char 0) ? -- ___ Python tracker __

[issue20453] json.load() error message changed in 3.4

Serhiy Storchaka added the comment: Yes, the change is deliberate (issue16009). -- nosy: +ezio.melotti, pitrou, rhettinger, serhiy.storchaka ___ Python tracker ___ __

[issue20453] json.load() error message changed in 3.4

New submission from Barry A. Warsaw: 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