You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2019-11-24.13:06:26.688>created_at=<Date2019-11-18.00:53:54.937>labels= ['3.8', 'library']
title='TypedDict: no way to tell which (if any) keys are optional at runtime'updated_at=<Date2019-11-24.13:06:26.687>user='https://github.com/Zac-HD'
classA(typing.TypedDict):
a: int# a is requiredclassB(A, total=False):
b: bool# a is required, b is optionalclassC(B):
c: str# a is required, b is optional, c is required again
PEP-589 is clear about the semantics, and this is obvious enough when reading the code. At runtime the __annotations__ attribute of each class gives us the set of allowed keys and the type of each corresponding value, but we have a problem:
C has __total__==True, but b is not actually required.
B has __total__==False, but a *is* required.
I can't see any way to get the parent classes of a TypedDict class!
The _TypedDictMeta metaclass updates the attributes, but leaves no record of the parent type - at runtime A, B, and C all appear to inherit directly from dict.
After discussion on the typing-sig mailing list, I propose to add __required_keys__ and __optional_keys__ attributes to TypedDict subclasses, as frozensets of strings.
This will be very useful for Hypothesis' from_type() strategy, as well as for type-based validation frameworks like pydantic or typeguard.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: