Skip to content

gh-136216: Update RFC references for the JSON format from RFC 7159 to RFC 8259 #151668

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
serhiy-storchaka wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −4
Open

gh-136216: Update RFC references for the JSON format from RFC 7159 to RFC 8259 #151668

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions Doc/library/json.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
--------------

`JSON (JavaScript Object Notation) <https://json.org>`_, specified by
:rfc:`7159` (which obsoletes :rfc:`4627`) and by
:rfc:`8259` (which obsoletes :rfc:`7159`) and by
`ECMA-404 <https://ecma-international.org/publications-and-standards/standards/ecma-404/>`_,
is a lightweight data interchange format inspired by
`JavaScript <https://en.wikipedia.org/wiki/JavaScript>`_ object literal syntax
Expand Down Expand Up @@ -632,7 +632,7 @@ Exceptions
Standard Compliance and Interoperability
----------------------------------------

The JSON format is specified by :rfc:`7159` and by
The JSON format is specified by :rfc:`8259` and by
`ECMA-404 <https://ecma-international.org/publications-and-standards/standards/ecma-404/>`_.
This section details this module's level of compliance with the RFC.
For simplicity, :class:`JSONEncoder` and :class:`JSONDecoder` subclasses, and
Expand All @@ -652,8 +652,9 @@ default settings.
Character Encodings
^^^^^^^^^^^^^^^^^^^

The RFC requires that JSON be represented using either UTF-8, UTF-16, or
UTF-32, with UTF-8 being the recommended default for maximum interoperability.
The RFC requires that JSON exchanged between systems that are not part of a
closed ecosystem be encoded using UTF-8 for maximum interoperability. Earlier
specifications of JSON also permitted the use of UTF-16 and UTF-32.

As permitted, though not required, by the RFC, this module's serializer sets
*ensure_ascii=True* by default, thus escaping the output so that the resulting
Expand Down
Loading