Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

gh-136216: Update JSON RFC references from 7159 to 8259#144453

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.

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

Already on GitHub?Sign in to your account

Open
kovan wants to merge1 commit intopython:main
base:main
Choose a base branch
Loading
fromkovan:gh-136216-json-rfc-update
Open
Changes fromall commits
Commits
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
10 changes: 5 additions & 5 deletionsDoc/library/json.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -12,7 +12,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 DownExpand Up@@ -615,7 +615,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 DownExpand Up@@ -704,7 +704,7 @@ Top-level Non-Object, Non-Array Values
The old version of JSON specified by the obsolete :rfc:`4627` required that
the top-level value of a JSON text must be either a JSON object or array
(Python :class:`dict` or :class:`list`), and could not be a JSON null,
boolean, number, or string value. :rfc:`7159` removed that restriction, and
boolean, number, or string value. :rfc:`8259` removed that restriction, and
this module does not and has never implemented that restriction in either its
serializer or its deserializer.

Expand DownExpand Up@@ -833,8 +833,8 @@ Command-line options

.. rubric:: Footnotes

.. [#rfc-errata] As noted in `the errata for RFC7159
<https://www.rfc-editor.org/errata_search.php?rfc=7159>`_,
.. [#rfc-errata] As noted in `the errata for RFC8259
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Be careful here. Is it still the correct errata?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I didn't have an answer here. I'm surprised that both RFCs have the same errata.

<https://www.rfc-editor.org/errata_search.php?rfc=8259>`_,
JSON permits literal U+2028 (LINE SEPARATOR) and
U+2029 (PARAGRAPH SEPARATOR) characters in strings, whereas JavaScript
(as of ECMAScript Edition 5.1) does not.
Loading
[8]ページ先頭
©2009-2026 Movatter.jp