The typical workflow is that you fork the peps repo and edit your file giving it number 9999. When you submit it as a PR, a PEP editor (probably me :-) will assign you a number and then it's a simple commit to change the number in the header and rename the file. This way we don't have to keep a database of assigned PEP numbers -- conflicts are resolved by repeating the process (though I don''t recall this has ever happened).

On Thu, Feb 4, 2021 at 6:45 AM David Foster <davidfstr@gmail.com> wrote:
On 1/31/21 12:25 AM, David Foster wrote:
> I have drafted an initial PEP for Required[...], a way to mark
> individual items of a TypedDict as required and allow defining a
> TypedDict with mixed required and potentially-missing items. See copy at
> the bottom of this email.

Silence is golden?

Can I get a PEP number? Then I can RST-ize it.

--
David Foster | Seattle, WA, USA
Contributor to TypedDict support for mypy


--
--Guido van Rossum (python.org/~guido)
Pronouns: he/him (why is my pronoun here?)