Hello all! I am new to Kedro and I was wondering what were the reasons behind the dependency management being handled with pip (+ requirements.txt and pip-compile to get a lock file) vs poetry. It seems to me poetry is becoming a standard in python dependency management and packaging. Anyone has an idea on this?

Hi! Kedro was started few years back, pip is at the time the standard. Requirements are mostly move to pyproject.toml now as this is more a standard (backed by a PEP and most package manager implement it). You may notice requirements.txt still exist because of some compatibility problem, I do expect it will disappear in the future.

In addition to what @Nok Lam Chan already said, Kedro aims to be easy to get into for new users. pip is the starting point for most people. Kedro doesn't prevent you in any way from using other alternatives.

It seems to me poetry is becoming a standard in python dependency management and packaging.

I was going to say, I disagree, but @Nok Lam Chan just beat me to it. 😄

To name a few more… uv (venv), pixi, conda, mamba

Thanks @Nok Lam Chan! I understand your points and I did not mean it was already a standard in that sense. I guess, it's just that within my working environment it's fairly rare to see a newly started python project using pure pip + requirements.txt like what you get when you do

kedro new

. In practice, I often see project started with indeed conda, poetry, and pixi when it's cross-platform.

I agree Poetry will sadly not become a standard, because it's not standards-compliant. uv/rye will probably be that though. still, we're very barebones in Kedro and, as you saw, we basically provide a plain

requirements.txt

Thanks @Juan Luis! I just read a bit about kedro starters today. If I wanted to create my own project template using poetry would I need to create my own?

@Guillaume Tauzin yes - at the moment I haven’t seen any community-contributed Kedro + poetry starters

Thanks @Juan Luis!

👀 thanks a lot for flagging! opening an issue for our website