PEP: <REQUIRED: pep number> Title: <REQUIRED: pep title> Author: <REQUIRED: list of authors' real names and optionally, email addrs> Sponsor: <real name of sponsor> PEP-Delegate: <PEP delegate's real name> Discussions-To: <REQUIRED: URL of current canonical discussion thread> Status: <REQUIRED: Draft | Active | Accepted | Provisional | Deferred | Rejected | Withdrawn | Final | Superseded> Type: <REQUIRED: Standards Track | Informational | Process> Topic: <Governance | Packaging | Release | Typing> Content-Type: text/x-rst Requires: <pep numbers> Created: <date created on, in dd-mmm-yyyy format> Python-Version: <version number> Post-History: <REQUIRED: dates, in dd-mmm-yyyy format, and corresponding links to PEP discussion threads> Replaces: <pep number> Superseded-By: <pep number> Resolution: <url>

[A short (~200 word) description of the technical issue being addressed.]

[Clearly explain why the existing language specification is inadequate to address the problem that the PEP solves.]

[Describe why particular design decisions were made.]

[Describe the syntax and semantics of any new language feature.]

[Describe potential impact and severity on pre-existing code.]

[How could a malicious user take advantage of this new feature?]

[How to teach users, new and experienced, how to apply the PEP to their work.]

[Link to any existing implementation and details about its state, e.g. proof-of-concept.]

[Why certain ideas that were brought while discussing this PEP were not ultimately pursued.]

[Any points that are still being decided/discussed.]

[A collection of footnotes cited in the PEP, and a place to list non-inline hyperlink targets.]

This document is placed in the public domain or under the CC0-1.0-Universal license, whichever is more permissive.