Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PEP 761: Deprecating PGP signatures for CPython artifacts #4027

Merged
merged 7 commits into from
Oct 9, 2024

Conversation

sethmlarson
Copy link
Contributor

@sethmlarson sethmlarson commented Oct 8, 2024

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--4027.org.readthedocs.build/pep-0761/

@sethmlarson sethmlarson requested a review from a team as a code owner October 8, 2024 14:19
@sethmlarson sethmlarson changed the title PEP 760: Deprecating PGP signatures for CPython artifacts PEP 761: Deprecating PGP signatures for CPython artifacts Oct 8, 2024
@sethmlarson
Copy link
Contributor Author

760 was already reserved (sorry!) so I bumped to 761.

Copy link
Member

@hugovk hugovk left a comment

Choose a reason for hiding this comment

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

Thank you!

Please also wrap the text:

Lines should usually not extend past column 79, excepting URLs and similar circumstances.

https://peps.python.org/pep-0012/#general

@hugovk hugovk added the new-pep A new draft PEP submitted for initial review label Oct 8, 2024
@hugovk
Copy link
Member

hugovk commented Oct 9, 2024

Thanks Seth and Jelle!

@hugovk hugovk merged commit 3e2f25f into python:main Oct 9, 2024
6 checks passed
@sethmlarson sethmlarson deleted the deprecate-pgp branch October 9, 2024 12:30
gvanrossum pushed a commit to gvanrossum/peps that referenced this pull request Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-pep A new draft PEP submitted for initial review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants