Skip to content

PEP 819: Disambiguate JSON parsing and make new files required #4773

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
emmatyping wants to merge 3 commits into
base: main
Choose a base branch
from
Open

PEP 819: Disambiguate JSON parsing and make new files required #4773

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9de2962
PEP 819: Add information about duplicate keys and integer parsing
emmatyping Jan 7, 2026
f0f830b
Also make the JSON files required
emmatyping Jan 7, 2026
07fa915
Discuss int values in security section
emmatyping Jan 7, 2026
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
Prev Previous commit
Next Next commit
Also make the JSON files required
  • Loading branch information
@emmatyping @emmatyping-nv
emmatyping authored and emmatyping-nv committed Jan 7, 2026
commit f0f830b394ef51cbbf1b8e7a10e0c063c2f3c73c
17 changes: 13 additions & 4 deletions peps/pep-0819.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,8 +118,8 @@ Specification
JSON Format Core Metadata File
------------------------------

A new optional but recommended file ``METADATA.json`` shall be introduced as a
metadata file for Python distribution packages. If generated, the ``METADATA.json`` file
A new required file ``METADATA.json`` shall be introduced as a
metadata file for Python distribution packages. The ``METADATA.json`` file
MUST be placed in the same directory as the current email formatted
``METADATA`` or ``PKG-INFO`` file.

Expand Down Expand Up @@ -200,8 +200,8 @@ encoded core metadata file MUST be served at
JSON Format Wheel Metadata File
-------------------------------

A new optional but recommended file ``WHEEL.json`` shall be introduced as a
JSON encoded version of the ``WHEEL`` file. If generated, the ``WHEEL.json``
A new required file ``WHEEL.json`` shall be introduced as a
JSON encoded version of the ``WHEEL`` file. The ``WHEEL.json``
file MUST be placed in the same directory as the current key-value formatted
``WHEEL`` file, i.e. the ``.dist-info`` directory. The semantic contents of
the ``WHEEL`` and ``WHEEL.json`` files MUST be equivalent. The wheel file
Expand Down Expand Up @@ -348,6 +348,15 @@ format, JSON has been chosen for a few reasons:
#. JSON is fast to parse and emit.
#. JSON schemas are JSON native and commonly used.

Make the JSON Package Metadata Files Optional
---------------------------------------------

A future major revision of the wheel format specification may make the
``METADATA.json`` and ``WHEEL.json`` files the default. Therefore, tools should
begin generating and consuming JSON package metadata files to ensure tools are
prepared for the future transition to the JSON package metadata files being
the default.


Open Issues
===========
Expand Down
Loading