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 akira
Recipients Julian, akira, cvrebert, ezio.melotti, jleedev, ncoghlan, pitrou, rhettinger, serhiy.storchaka, vstinner
Date 2014-05-16.02:39:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Both json standard (ECMA-404) [1] and the new json rfc 7159 [2] do not mention
the encoding detection.


From the rfc:

> JSON text SHALL be encoded in UTF-8, UTF-16, or UTF-32.  The default
  encoding is UTF-8, and JSON texts that are encoded in UTF-8 are
  interoperable in the sense that they will be read successfully by the
  maximum number of implementations; there are many implementations
  that cannot successfully read texts in other encodings (such as
  UTF-16 and UTF-32).

  Implementations MUST NOT add a byte order mark to the beginning of a
  JSON text.  In the interests of interoperability, implementations
  that parse JSON texts MAY ignore the presence of a byte order mark
  rather than treating it as an error.
Date User Action Args
2014-05-16 02:39:43akirasetrecipients: + akira, rhettinger, ncoghlan, pitrou, vstinner, ezio.melotti, cvrebert, Julian, serhiy.storchaka, jleedev
2014-05-16 02:39:43akirasetmessageid: <>
2014-05-16 02:39:43akiralinkissue17909 messages
2014-05-16 02:39:41akiracreate