Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Screenshot 2025-01-25 at 5.23.55 PM.png

I am having type issues with prefect flows. Anyone know what might be the root cause?
Pylance reports the following:
No overloads for "__call__" match the provided arguments
  Argument types: (str)Pylance<https://github.com/microsoft/pyright/blob/main/docs/configuration.md#reportCallIssue|reportCallIssue>

Filed a bug with more details
<https://github.com/PrefectHQ/prefect/issues/16856>

It’s still a bug for sure, but if you do task() does it type properly?

Screenshot 2025-01-25 at 6.12.01 PM.png

Screenshot 2025-01-25 at 6.13.08 PM.png

Is this setup unlike how I would actually define tasks once I am really using this?

or does everyone just silence type errors with prefect?

&gt; does everyone just silence type errors
Nah — I think the quick start needs some updating to have better typing itself.

Like hello_world should be name: str = “world” and so should print_hello. My suspicion is that the decorators are now strongly typed so our outdated untyped decorators are complaining. 

Screenshot 2025-01-25 at 6.31.43 PM.png

Adding type hints everywhere doesn't affect this

Screenshot 2025-01-25 at 6.33.57 PM.png

is submitting tasks the preferred method? This seems to quiet the errors

when I pip install 3.1.10 everything types just fine, but start seeing wonkiness in 3.1.11 -- good catch