PEP 566 -- Metadata for Python Software Packages 2.1 | Python.org specifies how to encode core metadata in JSON. Is this just an FYI thing in case people need help encoding the data from e.g.
METADATA, or is/was there a desire to try and slowly move the community over to JSON for storing this information?
I ask because I noticed two things. One, PEP 566 doesn’t specify a file name that could be used if a build tool chose to include a JSON version of
METADATA or if an installer decided to add such data itself post-install (e.g. Flit and
installer, respectively). Two, reading over Recording installed projects — Python Packaging User Guide made me notice that
METADATA is the one file format that is intrinsically tied to Python’s stdlib (you could argue CSVs are not a standard, but the core metadata spec explicitly calls out
email.parser as how you’re expected to support reading core metadata while I think how CSVs should be formatted is well understood).