PEP 750: major updates to "Template Strings" based on community feedback

[davepeck]

• Change is either:
  • To a Draft PEP
  • To an Accepted or Final PEP, with Steering Council approval
  • To fix an editorial issue (markup, typo, link, header, etc)
• PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

This PR contains substantial updates to PEP 750 based on feedback from the broader Python community, including comments on the official PEP Discourse thread and in-person core team feedback at the recent Bellevue, WA, USA sprint.

It has been reviewed by:

• @lysnikolaou (in progress)
• @pauleveritt
• @jimbaker
• @koxudaxi
• @davepeck

Koudai Aono (@koxudaxi) and I were both added as co-authors.

---

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 (not relevant?)
• Right before or after initial merging, PEP discussion thread created and linked to in Discussions-To and Post-History (the existing Discourse thread is found here )

---

📚 Documentation preview 📚: https://pep-previews--4062.org.readthedocs.build/pep-0750/

[AA-Turner]

Thank you for putting up with me @davepeck! This seems in a good state to merge (I've left a comment on templatelib on the thread, but it's non editorial.)

Do you have anything outstanding before merging? We should probably get this in before it hits 200 commits, and anything missed can be covered in a follow up.

Thank you again!

A

[davepeck]

Thank you for putting up with me @davepeck!

On the contrary, thank you for putting up with me and my zillion edits! :-)

This seems in a good state to merge (I've left a comment on templatelib on the thread, but it's non editorial.)

Yes, at this point, I think we can merge. We'll need another turn of the crank for sure, but it's in a good place for now.

[AA-Turner]

Thanks @davepeck!

A