PEP 732: The Python Documentation Editorial Board

[jablonskidev]

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

---

📚 Documentation preview 📚: https://pep-previews--3489.org.readthedocs.build/pep-0732/

[hugovk]

Please use PEP number 732. 📚

[jablonskidev]

Thank you for your feedback and patience. The PEP now has the correct number and date. I also changed "DevGuide" to "devguide" to follow house style. Please let me know if you need any further action from me.

[hugovk]

Thanks! I think we're almost there.

Please also update the .github/CODEOWNERS file with:

peps/pep-0732.*    @Mariatta

[jablonskidev]

I applied your feedback. Please let me know if you need anything else.

[Mariatta]

Thanks!

[hugovk]

Finishing touches :)

[hugovk]

Thank you!