PEP 807: Index support for Trusted Publishing

[woodruffw]

Pre-PEP thread: https://discuss.python.org/t/pre-pep-trusted-publishing-token-exchange/103067/15

Donald (@dstufft) has graciously agreed to be my sponsor and delegate for this PEP 🙂

Signed-off-by: William Woodruff william@astral.sh

Basic requirements (all PEP Types)

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

Standards Track requirements

• PEP topic discussed in a suitable venue with general agreement that a PEP is appropriate
• Suggested sections included (unless not applicable)
  • Motivation
  • Rationale
  • Specification
  • Backwards Compatibility
  • Security Implications
  • How to Teach This
  • Reference Implementation
  • 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--4597.org.readthedocs.build/pep-0807/

[hugovk]

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

@dstufft Please could you confirm your sponsorship?

[AA-Turner]

You can take 807.

A

[willingc]

Thanks @woodruffw. Overall this looks good and I like your approach to standardize the workflow.

[dstufft]

Please could you confirm your sponsorship?

Yes.

[woodruffw]

Let me know if anything else is needed here for merge!

(I'm holding off on the DPO thread until this is live.)

[AA-Turner]

A few points:

I don't think you say what 'pytp' means anywhere -- presumably 'Python Trusted Publishing'? I assume the acronym form was chosen over spelling out '/trusted-publishing/' for length reasons?

Please remove all the reference targets and/or prefix them with pep807-. You can replace :ref: by just using the section name (e.g. `Section Name`_).

A

[woodruffw]

I don't think you say what 'pytp' means anywhere -- presumably 'Python Trusted Publishing'? I assume the acronym form was chosen over spelling out '/trusted-publishing/' for length reasons?

Yeah, I just made that up 😅 -- I don't actually like it, but I was going to flag it for ideation/bikeshedding on the DPO thread itself. It does indeed stand for "Python Trusted Publishing."

[woodruffw]

Thanks @AA-Turner! LMK if it's easier for me to deconflict here (I know it's pretty annoying with the PR-to-an-org-fork workflow...)

[AA-Turner]

@woodruffw please, sorry I hadn't noticed the merge conflicts.

A

[woodruffw]

Done!

[AA-Turner]

Thanks!

A