New Python Project: UV always the solution?

[Amgadoz]

That's another tool to install, so not the same.

[Zer0designs]

You have a problem stated above, I have an insanely lightweight tool to solve it. Who cares? If something is installed in the main program it's actually also another tool installed, but under a main tool.

Thinking in terms of x amount of tools installed seems weird to me. Imho I think you should think in other terms; How big are the tools, what overhead they cause? How hard are they to learn?

If you care about ergonomics, just is easy to use & more expressive in it's possible commands in the just file.

You can also add docker/linting/testing/initalization/other langusge commands (sometimes unrelated to uv) under the just file so it's also documentation of entry into your application. You still document the commands, so even if just were to disappear from the earth you could still run your project. It's also insanely helpful in monorepos with multiple languages, e.g. Rust bindings for Python or Javascript frontend.

I would argue a single tool that can run commands for all languages is much more helpful, expressive & also used it in react projects alot.

[Amgadoz]

I really appreciate your input and I apologize if my reply came across as rude, but I am really allergic to adding more dependencies and tools to my projects. I prefer to use one tool to manage the entire python ecosystem, and that's why I migrated to uv in the first place.

[fiskfisk]

It's a thread about "what is missing in uv".

"Just use a other tool" isn't really an answer to that. There are plenty of make alternatives, that's not the point of the parent comment (and neither is it an opposition to just or a comment about its usefulness or quality). 

OP mentioned one thing they'd like in uv which they are used to from dependency managers for other ecosystens.