o ,wik @s>dZddlmZddlmZddlmZdeddfdd ZdS) aThe materialize module makes implicit defaults explicit. Fiddle Buildable's allow accessing argument defaults, but they are treated differently by the systems compared to values that have been explicitly set (e.g. by a user's configuration). (This enables users and tooling to quickly see what has been configured explicitly.) For when a configuration is to be persisted for longer-term archival, materializing the defaulted values can make the configuration archive somewhat more hermetic. )Any)config)daglishvaluereturnNcCs"dtjfdd}tj||dS)aExplicitly sets values for defaulted arguments. Buildable makes a distinction between a defaulted argument that hasn't been set, and an argument that has been explicitly set to a value (that may or may not be the same as the argument's default value). However, there are some instances where it can be valuable to explicitly materialize the defaulted values (e.g. when persisting a configuration in a text format, or for certain visualizations). Calling `materialize_defaults` on a Buildable is the equivalent of doing `cfg.MY_ARG = cfg.MY_ARG` for all arguments with default values that have not yet had a value explicitly set. Args: value: A nested collection which may contain Buildable arguments. statecSs^t|tjr#|jjD]}|j|jur"|j|j vr"t ||j|jq |j |ddD]}q*dS)NT) ignore_leaves) isinstancer Buildable__signature_info__ parametersvaluesdefaultemptyname __arguments__setattryield_map_child_values)noderarg_rT/home/ubuntu/sommelier/.venv/lib/python3.10/site-packages/fiddle/_src/materialize.pytraverse5s z&materialize_defaults..traverseN)rStateMemoizedTraversalrun)rrrrrmaterialize_defaults"sr)__doc__typingr fiddle._srcrrrrrrrs