UV is a growing community. In my experiences, not quite as fully developed as poetry, but I haven't run into your exact painpoints. UV likely eventually the better move, so if it works now - seems like a decent time.
Black-vs-ruff is a no-brainer [ ruff is from the same group ]. I hadn't found the time difference with poetry-vs-uv to be a significant painpoint, but certainly doesn't hurt. On Mon, Jul 28, 2025 at 3:28 PM Alexander Sorokoumov < aleksandr.sorokou...@gmail.com> wrote: > Hey everyone, > > This change is significant, so I wanted to open a discussion about it > first. > > The main motivation for this change has been that the current Poetry > version does not support later Python versions and newer Poetry versions do > not support our current project config format. Since the build system > upgrade requires additional effort, I was wondering if it is time to shop > for an alternative and did find uv. > > In my opinion, uv is a more promising alternative for 2 reasons: > > 1. It follows an approach similar to build tools one can find in other > ecosystems (looking at Maven/Bazel/Gradle). It is a single entry-point to > manage dependencies, python versions, build and upload artifacts, etc. I > did not find a way to also run tests and benchmarks without tox/pytest, but > it is definitely a step in the right direction IMO. > 2. It is fast. I encourage reviewers to compare how long it takes to sync > dependencies or re-build a lock file with uv vs Poetry. > > I have opened a PR to showcase what the project will look like after this > change https://github.com/apache/otava/pull/80. > > Please let me know what you think. > > Best, > Alex >
