o 7ήc4 @sddlZddlmZmZmZmZmZmZddlm Z ddl m Z m Z ddlm Z mZer2ddlmZejdkrCd ed d efd d Zn ded efdd Zd ed ded edfddZdedded edfddZdS)N) TYPE_CHECKINGAnyDict FrozenSet NamedTupleTypeRequired) BaseModel create_model) is_typeddictis_typeddict_special) TypedDict) typeddict_clsrreturncCst|o t|jdkS)Ntyping)r type __module__)rr?/tmp/pip-target-vg8gfxp4/lib/python/pydantic/annotated_types.pyis_legacy_typeddict sr_cCsdS)NFr)rrrrrskwargsr c snt|ds tdt|rtdd|jDrtd|jfdd|jD}t|j fi||S)z Create a `BaseModel` based on the fields of a `TypedDict`. Since `typing.TypedDict` in Python 3.8 does not store runtime information about optional keys, we raise an error if this happens (see https://bugs.python.org/issue38834). __required_keys__zYou should use `typing_extensions.TypedDict` instead of `typing.TypedDict` with Python < 3.9.2. Without it, there is no way to differentiate required and optional fields when subclassed.css|]}t|VqdSN)r).0trrr )s z.create_model_from_typeddict..zYou should use `typing_extensions.TypedDict` instead of `typing.TypedDict` with Python < 3.11. Without it, there is no way to reflect Required/NotRequired keys.cs&i|]\}}|||vrtndfqSrr r field_name field_type required_keysrr 2sz/create_model_from_typeddict..) hasattr TypeErrorrany__annotations__valuesritemsr __name__)rrfield_definitionsrr$rcreate_model_from_typeddicts  r/namedtuple_clsrcKsDt|ddp dd|jD}dd|D}t|jfi||S)z Create a `BaseModel` based on the fields of a named tuple. A named tuple can be created with `typing.NamedTuple` and declared annotations but also with `collections.namedtuple`, in this case we consider all fields to have type `Any`. r*NcSsi|]}|tqSr)r)rkrrrr&Bsz0create_model_from_namedtuple..cSsi|] \}}||tfqSrr r!rrrr&Es)getattr_fieldsr,r r-)r0rnamedtuple_annotationsr.rrrcreate_model_from_namedtuple:sr5)sysrrrrrrrfieldsr mainr r r rtyping_extensionsr version_infoboolrr/r5rrrrs$     "$