pyproject.toml

Lute uses pyproject.toml for packaging, and so the requirements are also specified in the .toml file.

Note: I'm not experienced with pyproject.toml, so below is my current understanding. In fact, I rather dislike the handling of dependencies in toml, as unpinned dependencies could create runtime issues.

The full requirements are in requirements.txt, so use pipdeptree to pull out the requirements in a consumable fashion for the toml file:

pipdeptree --freeze

and then manually determine what should go into the [project][dependencies] and dev.

Note I take the requirements.txt == entries and change them to >=x,<y, assuming that future changes up until the next major release for that package are backwards-compatible. E.g, the dependency for Flask-SQLAlchemy==3.1.1 in requirements.txt becomes Flask-SQLAlchemy>=3.1.1,<4.