Antony Milne

## Notes from technical design discussion on 10 August * **Cost-benefit of doing the split.** In general several people did not feel convinced that the cost of this work (engineering...

Following a discussion between @idanov, @AntonyMilneQB, @AhdraMeraliQB and @noklam this afternoon, here's where things stand: 1. Circular dependencies was indeed deemed to be an issue with the current approach. The...

This is great! 🚀 Just to wanted another motivation for doing this, and also some more tasks that will be needed. Datasets and their dependencies are the number 1 cause...

> I think there's two options here: > > 1. Actually try running the pipeline, and get the expected error message associated with running a pipeline with no nodes. >...

Also, if we do maintain (or adopt) the pattern that `kedro xyz` corresponds to `xyz.feature` then let's rename the file `new.feature` (and similarly for any other misnamed files).

P.S. @deepyaman do you still need to fork kedro to make a PR?

Very good point @noklam, thanks for the testing! I had thought of this case before but then forgotten all about it... Ideally I think a very simple project like `pandas-iris`...

> Quick question, does `kedro new` (with no starters) generate a project with `find_pipelines`? Yes.

Agree that it would be nice to make the rich settings more configurable, but I don't think pyproject.toml would be the right place for this. I have some ideas for...

Currently the rich setup does three slightly different things (see [`_ProjectLogging`](https://github.com/kedro-org/kedro/blob/ef7ccb1f80d9f45220db34e236e028e91d14a4ad/kedro/framework/project/__init__.py#L189)): 1. logging: `rich.logging.RichHandler` in logging.yml. This is both framework- and project-side 2. traceback handling: `rich.traceback.install`. This is just framework-side...