This PEP [1] introduces syntax to mark individual keys of a TypedDict as
either required or potentially-missing. Previously the only way to have
a TypedDict with mixed required and non-required keys was to define two
TypedDicts - one with total=True and one with total=False - and have one
of those TypedDicts inherit from the other. This PEP introduces special
forms Required[] and NotRequired[] to the "typing" module that can be
used to directly mark individual items of a TypedDict as required or
not-required. We have implementations for mypy, pyright, and pyanalyze.
Consensus on the PEP has been reached in typing-sig.
My understanding of the PEP process as described in PEP 1 [2] is that
content review should be requested of core developers here in
python-dev. So consider this my official request for comments! ^_^
I believe that after review & feedback from python-dev the next step
would be to submit this PEP to the Steering Council. However it's not
clear to me from [2] where I should actually do that when the time comes.
--
David Foster | Seattle, WA, USA
Contributor to TypedDict support for mypy
[1]: https://www.python.org/dev/peps/pep-0655/
[2]: https://www.python.org/dev/peps/pep-0001/#pep-review-resolution
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/C7QCZ5J277O5WHDJF5PFTA453DY7DS7S/
Code of Conduct: http://python.org/psf/codeofconduct/
