How to use a non-dynamic `input_namespace`

sphuber · December 6, 2024, 12:04pm

This because setting valid_type to a particular value, automatically makes the namespace dynamic:

aiidateam/plumpy/blob/55e05e956c9715fb69785d83d0194b65811b4720/src/plumpy/ports.py#L397


      
          @valid_type.setter
          def valid_type(self, valid_type: Optional[Type[Any]]) -> None:
              """Set the `valid_type` for the `PortNamespace`.
          
              If the `valid_type` is None, the `dynamic` property will be set to `False`, in all other cases `dynamic` will be
              set to True.
          
              :param valid_type: a tuple or single valid type that the namespace accepts
              """
              if valid_type is not None:
                  self.dynamic = True
          
              super(PortNamespace, self.__class__).valid_type.fset(self, valid_type)  # type: ignore
          
          @property
          def populate_defaults(self) -> bool:
              return self._populate_defaults
          
          @populate_defaults.setter
          def populate_defaults(self, populate_defaults: bool) -> None:
              self._populate_defaults = populate_defaults

Not sure if this is part of the aiida-core docs, but may be useful to add if not yet the case.

Topic		Replies	Views
How to validate two process inputs using validator? General Usage question	2	101	July 10, 2023
Aiida-workgraph: How to handle dynamic inputs and outputs of tasks General Usage	10	247	August 30, 2024
On the dynamic change of workchain process class inputs General Usage	2	55	November 4, 2024
Show stored data in provenance graph Developer plugin	5	99	April 19, 2024
Exposing dynamic outputs using labels from Calculations? General Usage	3	125	May 14, 2024

How to use a non-dynamic `input_namespace`

Related topics