> Even if you don't think this is a great use case, or your sweet spot, it's important to realize that it is very, very common, and when your users hit it they

> Even if you don't think this is a great use case, or your sweet spot, it's important to realize that it is very, very common, and when your users hit it they will look up how to deal with it. When the answer is "we can't help you here" that's extremely disappointing, and that will motivate users to leave. Hamilton doesn't support that, but it hasn't made a decision decision that would prevent that :) Yeah I'm definitely going to dive deeper into Luigi. Thanks for the rec. Especially wondering now whether it abstracts things as data types, or some other way... As an aside, you might like checking out redun, the influences section is particularly enlightening as to what other systems there are - https://insitro.github.io/redun/design.html#influences https://insitro.github.io/redun/design.html#influences