Skip to content

Core Metadata: Remove line suggesting metadata produces should use outdated versions - #1063

Draft
CAM-Gerlach wants to merge 1 commit into
pypa:mainfrom
CAM-Gerlach:core-metadata-rm-lower-version
Draft

CAM-Gerlach wants to merge 1 commit into
pypa:mainfrom
CAM-Gerlach:core-metadata-rm-lower-version

Conversation

@CAM-Gerlach

@CAM-Gerlach CAM-Gerlach commented Mar 14, 2022 •

Copy link
Copy Markdown
Contributor

Presently, the Metadata-Version section of the core metadata spec states:

For broader compatibility, build tools MAY choose to produce distribution metadata using the lowest metadata version that includes all of the needed fields.

Following discussion on PEP 685's thread and related conversations on metadata-version, it seemed prudent to simply remove this; per @pfmoore

I would prefer to drop the quoted statement, and let the whole thing come under the “be strict in what you produce and lenient in what you consume” principle, so that metadata producers should always produce the latest version that they can, and consumers should be capable of dealing with older versions.

PEP 609 in turn delegates to the the PyPA Specifications document, which states:

All enhancements proposed this way must be discussed on the Packaging category of the Python.org Discourse prior to amending the PEP

I opened a thread on the packaging discourse to gather consensus and any objections to this change.

@CAM-Gerlach CAM-Gerlach changed the title Core Metadata: Rm line allowing metadata producers to use lower versions Core Metadata: Remove line suggesting metadata produces should use outdated versions Mar 14, 2022

@merwok merwok left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

One approval on the forum, no opposition.

PR title typo: producers*

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants