+ NV-j3a0t$Rt^RIHt^RIt^RIt^RIt^RIt^RI H t ^RI H t ^RI Ht^RIHtHtHtHtHt^RIHtHtHtHt^RIHtHt^R IHt^R IH t ^R I!H"t"H#t#^R IH$t$^R I%H&t&H't'^RI(H)t)^RI*H+t+H,t,^RI-H.t.^RI/H0t0^RI1H2t2^RI3H4t4^RI5H6t6]'d^RI7H8t9^RI:H;t;!RR]9]4tR"R#lt?R$R%lt@]A]B]P],3,tDR&]ER'&] R(R)l4tFR#)+z0Private logic for creating pydantic dataclasses.) annotationsN) Generator)contextmanager)partial) TYPE_CHECKINGAnyClassVarProtocolcast) ArgsKwargsSchemaSerializerSchemaValidator core_schema) TypeAliasTypeIs)PydanticUndefinedAnnotation) FieldInfo)PluggableSchemaValidatorcreate_schema_validator)PydanticDeprecatedSince20)_config _decorators)collect_dataclass_fields)GenerateSchemaInvalidSchemaError)get_standard_typevars_map)set_dataclass_mocks) NsResolver)generate_pydantic_signature)LazyClassAttribute)DataclassInstance) ConfigDictcx]tRt^(t$RtR]R&R]R&R]R&R]R &R ]R &R ]R &R]R&]RRl4tRtR#)PydanticDataclassa!A protocol containing attributes only available once a class has been decorated as a Pydantic dataclass. Attributes: __pydantic_config__: Pydantic-specific configuration settings for the dataclass. __pydantic_complete__: Whether dataclass building is completed, or if there are still undefined fields. __pydantic_core_schema__: The pydantic-core schema used to build the SchemaValidator and SchemaSerializer. __pydantic_decorators__: Metadata containing the decorators defined on the dataclass. __pydantic_fields__: Metadata about the fields defined on the dataclass. __pydantic_serializer__: The pydantic-core SchemaSerializer used to dump instances of the dataclass. __pydantic_validator__: The pydantic-core SchemaValidator used to validate instances of the dataclass. zClassVar[ConfigDict]__pydantic_config__zClassVar[bool]__pydantic_complete__z ClassVar[core_schema.CoreSchema]__pydantic_core_schema__z$ClassVar[_decorators.DecoratorInfos]__pydantic_decorators__zClassVar[dict[str, FieldInfo]]__pydantic_fields__zClassVar[SchemaSerializer]__pydantic_serializer__z4ClassVar[SchemaValidator | PluggableSchemaValidator]__pydantic_validator__cV^8dQhRR/#)returnbool)formats"p/Volumes/fast/ai/experiments/ui-tars-smoke/.venv/lib/python3.14/site-packages/pydantic/_internal/_dataclasses.py __annotate__PydanticDataclass.__annotate__>s :::c R#Nr/clss&r1__pydantic_fields_complete__.PydanticDataclass.__pydantic_fields_complete__=s7:r4r/N) __name__ __module__ __qualname____firstlineno____doc____annotations__ classmethodr9__static_attributes__r/r4r1r#r#(sA 21--"BB!EE;;!;; TT : :r4r#c(V^8dQhRRRRRRRR/#) r,r8ztype[StandardDataclass]config_wrapper_config.ConfigWrapper ns_resolverNsResolver | Noner-Noner/)r0s"r1r2r2As0%% %)%#% %r4cB\V4p\WW1R7pW@nR#)zCollect and set `cls.__pydantic_fields__`. Args: cls: The class. config_wrapper: The config wrapper instance. ns_resolver: Namespace resolver to use when getting dataclass annotations. )rF typevars_maprDN)rrr()r8rDrFrJfieldss&&& r1set_dataclass_fieldsrLAs%-S1L % <F%r4 raise_errorsTrF _force_buildFc 0V^8dQhRRRRRRRRR RR R/#) r,r8 type[Any]rDrErMr.rFrGrNr-r/)r0s"r1r2r2UsLii i)i i # i  i ir4c VPpRRlpVP R2VnW`nVPVn\ WVR7V'g VP 'd\ V4R#\VR4'd\P!R\4\V4p\VVVR7p\R \\VVP VP"VP$R R 74VnVP)V4p TP/TP0R7p TP3T 4p \7RT4pYn\;YTP<TPRYP>4Tn \CY4Tn"R Tn#R # \*d/p T'dh\ TR T P, R 24R p ? R#R p ? ii;i \4d\ T4R#i;i)aJFinish building a pydantic dataclass. This logic is called on a class which has already been wrapped in `dataclasses.dataclass()`. This is somewhat analogous to `pydantic._internal._model_construction.complete_model_class`. Args: cls: The class. config_wrapper: The config wrapper instance. raise_errors: Whether to raise errors, defaults to `True`. ns_resolver: The namespace resolver instance to use when collecting dataclass fields and during schema building. _force_build: Whether to force building the dataclass, no matter if [`defer_build`][pydantic.config.ConfigDict.defer_build] is set. Returns: `True` if building a pydantic dataclass is successfully completed, `False` otherwise. Raises: PydanticUndefinedAnnotation: If `raise_error` is `True` and there is an undefined annotations. c(V^8dQhRRRRRRRR/#)r,__dataclass_self__r#argsrkwargsr-rHr/)r0s"r1r2(complete_dataclass..__annotate__vs0\\%6\s\c\VZ\r4cZRpTpVPP\W4VR7R#)T) self_instanceN)r*validate_pythonr )rSrTrU__tracebackhide__ss&*, r1__init__$complete_dataclass..__init__vs,     00D1IYZ0[r4z .__init__)rDrFF__post_init_post_parse__zVSupport for `__post_init_post_parse__` has been dropped, the method will not be called)rFrJ __signature__T)initrKvalidate_by_nameextra is_dataclass`N)titleztype[PydanticDataclass] dataclass)$r\r= config_dictr$rL defer_buildrhasattrwarningswarnrrrrrrr(rarbr_generate_schemarname core_configr; clean_schemarr r&rr<plugin_settingsr*r r)r%) r8rDrMrFrN original_initr\rJ gen_schemaschemaerns &&$$$ r1complete_dataclassruUs:LLM\ #//0 :HL,88CU N666C s.// d % -S1L!J+ '**+<< &&  C++C0!,,3<<,@K((0 (# .C#) !8S^^S%5%5{KQoQo"C#36"GC $C 1 '  C1QVVHA/  C s*;F)G G"#G  GG-,G-c V^8dQhRRRR/#)r,r8rPr-zTypeIs[type[StandardDataclass]]r/)r0s"r1r2r2s a aY a.M ar4cRRVP9;'d\VR4'*#)aJReturns `True` if the class is a stdlib dataclass and *not* a Pydantic dataclass. Unlike the stdlib `dataclasses.is_dataclass()` function, this does *not* include subclasses of a dataclass that are themselves not dataclasses. Args: cls: The class. Returns: `True` if the class is a stdlib dataclass, `False` otherwise. __dataclass_fields__r*)__dict__rir7s"r1is_stdlib_dataclassrzs& "S\\ 1 ` `'#G_:`6``r4c V^8dQhRRRR/#)r,pydantic_fieldrr-zdataclasses.Field[Any]r/)r0s"r1r2r2s++y+5K+r4c<RV/p\PR8dVPeVPVR&\PR8dVPeVPVR&VPRJdVPVR&\ P !R/VB#)defaultdockw_onlyTrepr)r r/)sys version_info descriptionrr dataclassesfield)r| field_argss& r1as_dataclass_fieldrs"+^! dataclass.Field(default=FieldInfo(repr=False), repr=True, ...) @pydantic_dc.dataclass class B(A): b: int = pydantic.Field(repr=False) ``` When passing `B` to the stdlib `@dataclass` decorator, it will look for fields in the parent classes and reuse them directly. When this context manager is active, `A` will be temporarily patched to be equivalent to: ```python {test="skip" lint="skip"} @stdlib_dc.dataclass class A: a: int = stdlib_dc.field(default=Field(repr=False), repr=False) ``` !!! note This is only applied to the bases of `cls`, and not `cls` itself. The reason is that the Pydantic dataclass decorator "owns" `cls` (in the previous example, `B`). As such, we instead modify the fields directly (in the previous example, we simply do `setattr(B, 'b', as_dataclass_field(pydantic_field))`). !!! note This approach is far from ideal, and can probably be the source of unwanted side effects/race conditions. The previous implemented approach was mutating the `__annotations__` dict of `cls`, which is no longer a safe operation in Python 3.14+, and resulted in unexpected behavior with field ordering anyway. :NNrxNTr)__mro__rygetitems isinstancer~rrrrappendr copyrr) r8original_fields_listbase dc_fields field_namer&dc_fields_with_pydantic_field_defaultsr~ new_dc_fieldrKoriginal_fieldsoriginal_fields & r1patch_base_fieldsrsn=? B7;}}7H7HI_ac7d &/__%62 %6! %--3 **6%--:O:O:OSXS`S`SeSemqSq J %6 /2  2 1 ' '([ \%K%Q%Q%S! y%--8 $yy/ ##w.7???+/L(<rs62  %%?? 00X0"-@0.(3&@#;-x;2%(i i &* i  iX a+$3 1 1# 667)7U4U4r4