PEP NNNN: d-string / Dedented Multiline Strings with Optional Language Hinting

[mardiros]

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--4410.org.readthedocs.build/

[hugovk]

And we also assign the PEP number after there's a sponsor, so I've set it to NNNN for now because another PEP may get 791 before this.

Please see https://peps.python.org/pep-0001/ for the PEP process.

[hugovk]

Thanks for the proposal, but it's been opened a bit early. See PEP 1, we do need discussion first. Let's close this PR, and let the discussion play out first.

By the way, you can still enable the CI and test this on your own fork if you like.

Don't hesitate to ask if you have any process questions that aren't clear from PEP 1. Thanks!

[mardiros]

Thanks for the proposal, but it's been opened a bit early. See PEP 1, we do need discussion first. Let's close this PR, and let the discussion play out first.

By the way, you can still enable the CI and test this on your own fork if you like.

Don't hesitate to ask if you have any process questions that aren't clear from PEP 1. Thanks!

Sorry for the mess, I understood that I have to open a PEP to open the discussion.

[hugovk]

No problem!

First start with an idea. Open a thread to discuss the idea. Once it seems there's consensus, and you find a sponsor, then you can submit the PEP as a PR here. Once merged and published on peps.python.org, another thread is opened to discuss the actual concrete draft PEP, and once there's consensus again there, it can be submitted to the steering council for a decision.

https://peps.python.org/pep-0001/#start-with-an-idea-for-python