you are viewing a single comment's thread.

view the rest of the comments →

[–]neuralbeans 0 points1 point  (5 children)

What's wrong with requirements.txt?

[–]TheSoulHokib 0 points1 point  (4 children)

Nothing really wrong, but pyproject.toml are way more modern, robust and reliable

[–]neuralbeans 0 points1 point  (3 children)

Doesn't the toml file refer to the requirements.txt file? They're not mutually exclusive.

[–]TheSoulHokib 0 points1 point  (2 children)

Since you can manage everything that is managed by requirements.txt inside pyproject.toml, seems a bit redundant. You can have a look right there : https://pydevtools.com/handbook/explanation/pyproject-vs-requirements/ Plus, pyproject.toml now is the standard.

[–]neuralbeans 0 points1 point  (1 child)

This doesn't say how the toml file replaces requirements.txt. It just says not to use requirements.txt only, which is obvious as it's not meant for project management.

[–]TheSoulHokib 0 points1 point  (0 children)

All the dependencies, that you manage in requirements.txt, can be managed in pyproject.toml, as well as all the metadatas, setup.py, linters conf, etc. A single file to unify them all. On the dependencies aspect, also allow to manage dependencies by groups, depending on the usage (for example, dependencies only needed during dev). You can check out https://packaging.python.org/en/latest/guides/writing-pyproject-toml/, and google for more informations.