Question on kedro starters: If I wanted to create a set of templates, with some functionality being common across them (like custom datasets, say - or full pipelines) - what are some approaches to keep this maintainable that work better than just copy-pasting the code between the starters?

So you can do

kedro pipeline create --template

for package templates

No easy, open-source answer (yet). You could build a custom library to assemble your templates from shared components. 🙂

I'm also toying with the thought of git submodules, that would preserve the raw python code being accessible, which I think might help with the target audience in my case.

Yeah the idea of two way editing is an interesting one, we’ve had some teams use symlinks. Since symlinks were rejected in PEP-660 we’ve erred on the proper packaging process