Use uv to manage and generate dependencies #4232
Conversation
|
@wes-otf I don’t have much context into the why we needed to add the explicit linux+cpu dependency, but if we would have to generate frozen requirements for translate as well, then doesn't it make sense to document the additional argument needed for pip? So instead of The documentation would say on Linux, use this instead. |
|
Now that we have converted these into pyproject dependencies, running |
frjo
added
Status: Needs dev testing 🧑💻
|
The deploy to Hypha Test on Heroku went without issues. |
@theskumar so this was specifically for the heroku deploy - I'm fine tossing whatever and making those options a branch-specific thing. whatever you think is best works for me! |
|
I believe using the |
Updated django v4.2.16 -> v4.2.17 Updated httpx v0.27.2 -> v0.28.0 Updated mkdocs-material v9.5.46 -> v9.5.47 Updated nh3 v0.2.18 -> v0.2.19 Updated phonenumberslite v8.13.50 -> v8.13.51 Updated pillow-heif v0.20.0 -> v0.21.0 Updated protobuf v5.29.0 -> v5.29.1 Updated pytest v8.3.3 -> v8.3.4 Updated ruff v0.8.0 -> v0.8.1 Updated six v1.16.0 -> v1.17.0
|
Merged main and
|
frjo
removed
Status: Needs testing
uvand pre-commit to automatically generate the locked requirements files from pyproject.toml.uv, uv doesn’t seem to be able to add--find-link=…to the exportedrequirements/translate.txt, for that reason the translation dependencies are left as they are and won’t be automatically exported via pre-commit.uv lock —upgradeis run, it will freeze the latest patch versions.~which means>=at the last digit of requirements.>=to make them easy to update, if something breaks in dev either fix it or go back to the old frozen dependencies.--no-depswhere applicable while installing these generated requirements as the sub-dependencies are already resolved.Test Steps