Advantages of using PDM over UV for new projects?

[paugier]

Sorry for this question, but I'd like to get a very old project (Mercurial) adopting a tool like PDM (in particular for lock files).

I'm used to PDM which is usually very good for my projects that already use it. However, here we really need to choose and I have to admit that I don't have too many arguments to choose PDM over UV.

The argument of speed for UV is quite strong.

I'm sure that Mercurial developers will be happy with using a tool written in Rust, since Mercurial is also written in Rust.

[klmcwhirter]

Don't take this as an authoritative answer, because I do not use all of PDM's features often. The one's I do use that uv is still missing (for now):

• tool.pdm.scripts - there are features that are in pdm scripts that other similar tools (e.g., just, go-task, etc.) do not have
• ironically, because it is written in python it is easier to extend with plugins
• builtin integration with / extensions for pytest - https://pdm-project.org/en/latest/dev/fixtures/

AND there is (experimental for now) integration with uv - so you can get the best of both.

I have tried poetry, pdm and uv. uv seems to be a little young yet. It will most certainly improve over the next several years. But I found myself back with pdm. It just feels right for a tool written in python managing python projects.

I can attest to the install / sync speed differential though.

I hope that helps.

And please do watch #3439. The uv project probably has a similar item.

[monchin]

Couldn't agree more. Scripts and hooks are incredibly convenient. I gave uv a try, but I eventually found myself back with pdm.

[paugier]

Thanks for your replies. This is also the experience that I have in 2025. We'll see how both projects evolve.