as well as the
object - which seems to be the proper choice. Now, when I start exploring this idea of
and connecting these task dependencies together, I get a little flustered without a more complex Prefect pipeline example... If it were possible, would you be able to point me to a larger scale example on GH or elsewhere; something that has multiple modules + a nicely defined project structure?
in this case you could just pass in
def add(x, y): return x + y def add_to_x(y): x = Parameter('x') total = task(add)(x, y) with Flow('flow') as f: add_to_x(1) add_to_x(2)
to the “factory” function instead, but in practice I have lots of parameters so it feels a bit clumsy. I’m sure there was a good reason for enforcing that parameters be unique; but doesn’t the fact that we’re able to assert that it’s unique mean that we could also just grab a reference to the already-existing task? 🤔
i am returning a class object; is this the reason for the doubly directed dependency arrow? it seems as though in all other tasks, where I am returning standard python data types, do not have a doubly...