feat: add METADATA 2.6 support (PEP 808)#1194
Merged
Merged
Conversation
henryiii
force-pushed
the
henryiii/feat/pep-808
branch
from
c264f7e to
a91069d
Compare
brettcannon
requested changes
May 25, 2026
Member
brettcannon
left a comment
brettcannon
left a comment
There was a problem hiding this comment.
We should probably have some test where reading metadata that falls under PEP 808 doesn't trigger an exception by having data and being listed in dynamic. Same goes for writing. Otherwise, if we ever decide to be more strict with dynamic we won't regress on PEP 808.
henryiii
force-pushed
the
henryiii/feat/pep-808
branch
from
a01df3e to
267b831
Compare
Add support for METADATA 2.6 as defined by PEP 808 - Including static values in dynamic metadata. This PEP relaxes constraints on dynamic metadata by allowing static portions of list/table fields to be defined alongside dynamic metadata. Since PEP 808 does not introduce any new metadata fields (only changes the semantic behavior of the Dynamic field in source distributions), the library only needs to recognize 2.6 as a valid metadata version. Changes: - Add "2.6" to _VALID_METADATA_VERSIONS and _MetadataVersion - Add Metadata 2.6 comment in RawMetadata - Update test fixtures and examples to use 2.6 - Update docs example to reference current version Assisted-by: OpenCode:NRP/kimi
Assisted-by: OpenCode:Kimi-K2.6 Signed-off-by: Henry Schreiner <henryfs@princeton.edu>
henryiii
force-pushed
the
henryiii/feat/pep-808
branch
from
267b831 to
1351523
Compare
brettcannon
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Should be an easy update here for PEP 808, just teaching packaging about the existence of METADATA 2.6.
🤖 Human guided, AI assisted PR (using this skill). AI text below. 🤖
Add support for METADATA 2.6 as defined by PEP 808 - Including static values in dynamic metadata. This PEP relaxes constraints on dynamic metadata by allowing static portions of list/table fields to be defined alongside dynamic metadata.
Since PEP 808 does not introduce any new metadata fields (only changes the semantic behavior of the Dynamic field in source distributions), the library only needs to recognize 2.6 as a valid metadata version.
Changes:
_VALID_METADATA_VERSIONSand_MetadataVersionRawMetadataAssisted-by: OpenCode:Kimi-K2.6