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 ezio.melotti
Recipients docs@python, ezio.melotti, jcea, mark.dickinson, nedbat, picomancer, pitrou, serhiy.storchaka, terry.reedy, tim.peters, vajrasky
Date 2014-02-10.08:10:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392019804.49.0.332708751899.issue19871@psf.upfronthosting.co.za>
In-reply-to
Content
I missed this comment from Serhiy:

> There are too many cases where json and Python syntax differ.

How many differences there are between the two?
I think we might add notes to the table at http://docs.python.org/3/library/json.html#encoders-and-decoders (either something similar to the notes in the table at http://docs.python.org/3/library/stdtypes.html#mutable-sequence-types, or just a couple of lines in a third column).  If there are too many differences and we follow the specs we can just add a note saying that the decoding is done according to the specs, add a link to them, and mention a few examples that are valid in Python but not in JSON (like Serhiy did in his message).
History
Date User Action Args
2014-02-10 08:10:04ezio.melottisetrecipients: + ezio.melotti, tim.peters, terry.reedy, jcea, mark.dickinson, pitrou, nedbat, docs@python, serhiy.storchaka, vajrasky, picomancer
2014-02-10 08:10:04ezio.melottisetmessageid: <1392019804.49.0.332708751899.issue19871@psf.upfronthosting.co.za>
2014-02-10 08:10:04ezio.melottilinkissue19871 messages
2014-02-10 08:10:03ezio.melotticreate