What’s the future for

kedro build-reqs

? Just saw the message that it will be deprecated at 0.19.

It will be removed from core Kedro, but you can still use it as it is nothing more than a thin wrapper of

pip-compile

Essentially it is

pip-compile --output-file=requirements.lock pyproject.toml

https://github.com/jazzband/pip-tools

thanks for the info 🙂

So @Nok Lam Chan when we update the

requirements.txt

file in future, what should we do? Run that

pip-compile

command? Is this something the docs need to be updated to explain, and if so, why are we removing it, since it's easier to type

kedro build-reqs

surely?

@Jo Stichbury I don’t have the full context as some of the user research happened before I joined. I think the main argument is that some of the CLI command usages are low, and do not justify the need to maintain them as they cause some trouble for our dependencies. Similar arguments go with

kedro test

, which is a thin wrapper of

pytest

User research GH Issue https://github.com/kedro-org/kedro/issues/1293

Ah, that's useful background, thanks @Nok Lam Chan!