[Core feature] Flytekit support for positional args

[kumare3]

Motivation: Why do you think this is important?

Curently only kwargs are supported

@task
def foo(x: int, y: int) -> int:
     ...

@workflow
def wf(x: int, y: int) -> int:
    return foo(x=x, y=y)

Goal: What should the final outcome look like, ideally?

Support positional args

@task
def foo(x: int, y: int) -> int:
     ...

@workflow
def wf(x: int, y: int) -> int:
    return foo(x, y)

Describe alternatives you've considered

NA

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

Flytekit does not support positional arguments when calling tasks within a workflow. Tasks must be invoked using keyword arguments only. This limitation is documented in a GitHub issue where it's stated that Flytekit requires keyword arguments to maintain clarity and avoid errors related to parameter ordering (GitHub issue #1339). There are no current plans to support positional arguments as per the discussions in the issue.

Would you like more detail on this topic or how to work with the current system using keyword arguments?

Sources:

• GitHub issue #1339

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[kumare3]

Then it will be possible to support

@task(unsafe=True)
def foo(*args, **kwargs) -> int:
     return int

[MortalHappiness]

#take