> > > This is why I asked, "how is this different from just putting > asyncio.run()" in the operator / task. > > Just wondering if it's really worth supporting async func when that's all > it does. >
Yep. I am not sure either - it has some nice properties (I kinda like explicitly marking the task as async - it's a very pythonic way, with a bit less boilerplate - you do not need to have separate async callable, all async code can be done inside @task - which is where you expect logic of @task decorated method to be, and it does not seem to complicate Airflow code much). But this is based on the assumption that we understand the proposal "entirety" correctly :). That's why I did the explicit example - because I have a strange feeling that there is more to this proposal than what my explicit example does. I think a good counter-example from David if that's the case might simply help to make sure we are all on the same page. J.
