PEP 717: Delegated Repository Authentication

[dstufft]

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
  • General topic has been discussed throughout many issue trackers over the years. This specific PEP was not, but have reached out to stakeholders in various projects, with no concerns about the design.
• 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--3172.org.readthedocs.build/pep-0717/

[dstufft]

Applied suggestions, thanks!

[CAM-Gerlach]

Sorry for the delay—I ended up having way too much on my plate to review this today, but I'll get to it tomorrow (er, later today by this point 😆 )

[AA-Turner]

@dstufft is this PEP ready to merge as an initial draft?

A

[JelleZijlstra]

@dstufft anything blocking this from being merged?

[ltuijnder]

Hi what is the status on this? It would be great if this PEP could get merged as it solves many open issues as outlined in the document.