Chinh (lelouvincx) / 2025-02-26

Note

• I’ve been using uv for a while now and I have some thoughts on it.
• First, it locks at the patch version. Given that users install dependencies from a lock file every day, this can be a problem. If a dependency releases a new patch version and the lock file is not updated, the user will have a different version installed than the one in the lock file. pip-compile for example, locks at the minor version by default. (can be configured to lock at the patch version, and vice versa)
• Second, the version release is so fast to the point that there is no breaking version to be aware of. I often receive a PR from dependabot to update the version, and I don’t know what’s changed. Plus, uv now has reached 0.6.x, which somehow gives me the feeling of unstable.
• Third, there are some compatibility issues with other tools like pre-commit, pip-tools, etc. This is understandable since uv is new and the ecosystem is not fully integrated yet. It works great standalone, but hard to integrate with other tools.
• Fourth, for migrating from pip-compile, there are some gotchas but the transition is smooth overall. However, for migrating from poetry, it’s a different story. The lock file format is different, and the way dependencies are resolved is different, you even have to change the workflow or how your CI/CD works.
• Finally, I don’t like the way uv handles the pyproject.toml file. It’s not as intuitive as poetry or pip-compile. Just a personal preference.

Done

• DONE Duty support RedDoorz.

DONE Write docker compose Prefect.

DONE Reply comment anh Triet.