Email or username:

Password:

Forgot your password?
7 comments
Rachael Ludwick

@jacob Strongly tempted to switch to uv because it seems the fastest path to unblocking my docker build with minimal other changes.

jacoBOOian πŸ‘»

@r343l I’d really encourage it, it’s really significantly better that everything out there, with almost no downsides.

Rachael Ludwick

@jacob the only downsides I can see (just off that blog) are:

- no cli run scripts from pyproject.toml. easily dealt with but mildly annoying
- we just finished moving from poetry to pdm

but pdm has a blocking issue and my main workaround is to use pyenv in my docker image (for running tests with reliable/fixed R and other binary deps) instead of system python at which point I have to change a lot anyway.

Chris is.

@r343l @jacob if you are using pdm to package your library, you don't need to change that to use uv; it'll use PDM's build system just fine.

Nearly every `pdm <foo>` command can be rewritten as `uv foo`.

Rachael Ludwick

@offby1 @jacob well ... in this case pdm is broken with system python on latest debian testing (trixie) and I can't move to debian stable for other reasons. I saw that one could swap uv in as the backend for pdm but it's not clear to me that it wouldn't still be broken.

Go Up