to avoid hijacking the thread, @Ben Horsburgh : https://kedro-org.slack.com/archives/C03R8N2M8KT/p1699261657794449?thread_ts=1698932258.475319&cid=C03R8N2M8KT yes! in fact we're now using both: we declare dependencies in

requirements.txt

and them read them in

pyproject.toml

https://github.com/kedro-org/kedro/blob/93dc1a91e4bb476287040ea3db4a610696cacb0c/k[…]project/%7B%7B%20cookiecutter.repo_name%20%7D%7D/pyproject.toml but you can also just avoid

requirements.txt

files entirely. what do you think of this approach?

Ah super interesting. How does the dynamic read behaviour work? Is it just a straight text read that is then deferred to

setuptools

to work, or is it still bound to

pip

? If the former - I love it! If the latter - still a broken system (what if I don't use

pip

)

the moment the metadata is read in

pyproject.toml

, and "frontend" (using PEP 517 frontend/backend terminology) can read it, not only pip. notice that

requirements.txt

can contain pip-specific syntax, like

--extra-index-url

for example. but in these cases, the dynamic reading just fails - only the subset that is "frontend agnostic" is supported. I'm wondering what alternative to

pip

are you using @Ben Horsburgh?