I think that uv is a _huge_ step forward in the Python ecosystem compared to Poetry/pip/pyenv/.... . As an illustration, here is the log of project setup inside a uv container - https://gist.github.com/Gerrrr/413dea7a47a278003ca41532e85572b8. TL;DR `uv sync --all-extras --dev` sets up the project for you without any gotchas. It installs _all_ necessary dependencies including ancient Python versions, tox, pytest, etc.
Best, Alex On Sat, Aug 2, 2025 at 1:07 PM Dave Fisher <w...@apache.org> wrote: > The ASF tooling team is working a project called Apache Trusted Releases. > We are switching to use uv. For the client we are developing it turns out > that it simple to install with pip and uv is engaged under the hood. > > See https://github.com/apache/tooling-releases-client/blob/main/README.md > for using pip to deploy to a venv from a GH repository. > > Best, > Dave > > > On Aug 1, 2025, at 4:31 AM, Henrik Ingo <hen...@old.nyrk.io> wrote: > > > > This is not my area of expertise and somehow I have a feeling uv and > poetry > > are similar in this regard... > > > > I would love to see a python tool that takes care of everything. To work > on > > Otava now, I first need to create a virtualenv with pyenv, then use > poetry > > to understand the .toml file, and in the end I'm pretty sure I did a pip > > install or something. I don't see the need for 3 separate tools. > > > > Reminds me of the days your would use easy_install to install pip :-D > > > > henrik > > > > On Tue, Jul 29, 2025 at 11:16 AM Joe Drumgoole <j...@joedrumgoole.com> > wrote: > > > >> I agree uv is faster and looks to be the emerging favourite. I looked at > >> supporting both, but it leads to a lot of duplication in pyproject.toml. > >> > >> +1 for uv. > >> > >> > >> Joe Drumgoole > >> > >> +087 2995547 > >> https://bsky.app/profile/joedrumgoole.com > >> > >> > >> > >> On Mon 28 Jul 2025, 23:28 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 > >>> > >> > >
