This is for a few reasons:
- opens the way for us to use
uv in GitHub actions, a better package manager (in my opinion) that will:
- unifies our developer dependencies with groups (so no more requirements.txt)
An example of a successful switch to pyproject.toml only: SuffolkLITLab/docassemble-EFSPIntegration#298. Would also consider putting the package in the latest docassemble playground and downloading the package, which should generate the correct MANIFEST.in (would have to make sure it doesn't mess up other entries in our pyproject.toml though).
This is for a few reasons:
uvin GitHub actions, a better package manager (in my opinion) that will:auditscan routinely: https://docs.astral.sh/uv/reference/cli/#uv-auditAn example of a successful switch to pyproject.toml only: SuffolkLITLab/docassemble-EFSPIntegration#298. Would also consider putting the package in the latest docassemble playground and downloading the package, which should generate the correct MANIFEST.in (would have to make sure it doesn't mess up other entries in our pyproject.toml though).