peps icon indicating copy to clipboard operation
peps copied to clipboard

PEP 808: Partially Dynamic Metadata

Open henryiii opened this issue 3 months ago • 4 comments

This PEP proposes an update to the pyproject.toml dynamic metadata specification to enable partially dynamic metadata, where some fields can be partially specified and also dynamically extended.

Pre-PEP thread: https://discuss.python.org/t/partially-dynamic-project-metadata-proposal-pre-pep/88608

Filipe (@FFY00) has graciously agreed to be my sponsor for this PEP.

Basic requirements (all PEP Types)

  • [x] Read and followed PEP 1 & PEP 12
  • [x] File created from the latest PEP template
  • [x] PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) and PEP header
  • [x] Title clearly, accurately and concisely describes the content in 79 characters or less
  • [x] Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval
  • [x] Author, Status (Draft), Type and Created headers filled out correctly
  • [x] PEP-Delegate, Topic, Requires and Replaces headers completed if appropriate
  • [x] Required sections included
    • [x] Abstract (first section)
    • [x] Copyright (last section; exact wording from template required)
  • [x] Code is well-formatted (PEP 7/PEP 8) and is in code blocks, with the right lexer names if non-Python
  • [x] PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML
  • [x] Authors/sponsor added to .github/CODEOWNERS for the PEP

Standards Track requirements

  • [x] PEP topic discussed in a suitable venue with general agreement that a PEP is appropriate
  • [x] Suggested sections included (unless not applicable)
    • [x] Motivation
    • [x] Rationale
    • [x] Specification
    • [x] Backwards Compatibility
    • [x] Security Implications
    • [x] How to Teach This
    • [x] Reference Implementation
    • [x] Rejected Ideas
    • [ ] Open Issues
  • [ ] Python-Version set to valid (pre-beta) future Python version, if relevant
  • [ ] Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
  • [ ] Right before or after initial merging, PEP discussion thread created and linked to in Discussions-To and Post-History

📚 Documentation preview 📚: https://pep-previews--4598.org.readthedocs.build/pep-0808/

henryiii avatar Sep 19 '25 13:09 henryiii

All commit authors signed the Contributor License Agreement.

CLA signed

python-cla-bot[bot] avatar Sep 19 '25 13:09 python-cla-bot[bot]

@LecrisUT, you need to sign the CLA, see above.

henryiii avatar Sep 19 '25 13:09 henryiii

  • [ ] Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval

@FFY00 Please could you confirm your sponsorship?

hugovk avatar Sep 29 '25 13:09 hugovk

@hugovk, I confirm :blush:

FFY00 avatar Oct 02 '25 13:10 FFY00

Is there anything else I need to do?

henryiii avatar Nov 14 '25 05:11 henryiii