Skip to content

Task API change: use tuple instead of set for input/output names #78

@poautran

Description

@poautran

In GitLab by @woutdenolf on Oct 23, 2025, 15:17 GMT+2:

When using required_input_names, optional_input_names etc. from Task we often need deterministic sorting: https://gitlab.esrf.fr/workflow/ewoks/ewokscore/-/merge_requests/277 (task discovery) and https://gitlab.esrf.fr/workflow/ewoks/ewokscore/-/merge_requests/320 (ewoks show).

I proposed to break the API and use tuples instead of sets.

Migrated from GitLab: https://gitlab.esrf.fr/workflow/ewoks/ewokscore/-/issues/78

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions