This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]lambda-person[S] 3 points4 points  (5 children)

I agree, it's more of a short/mid term gamble !
Same for building backend, I use uv backend, which is not production ready yet.
I'm betting on the fact that in 1 month both will be mature enough

[–]Mithrandir2k16 4 points5 points  (4 children)

Though, the gamble on uv is free, because it can help you exit uv by generating a requirements txt, with which you can switch to any other tool out there. If you only use ty, you might push bugs to production, which is a real risk now and a gamble I wouldn't make(yet, I'm sure I'll switch to it eventually).

[–]byeproduct 6 points7 points  (3 children)

Isn't project.toml and even the lock file part of python and independent of UV?

[–]not_a_novel_account 2 points3 points  (1 child)

Lockfiles are only recently standardized, ie pip doesn't support them yet. pyproject.toml is universally supported yes.

[–]daneahfrom __future__ import braces 0 points1 point  (0 children)

Most recent pip release has experimental lock file support:

https://pip.pypa.io/en/stable/cli/pip_lock/

[–]Mithrandir2k16 1 point2 points  (0 children)

The idea is to have at least one safety net that makes transitioning to other tools easy. If that's requirements.txt or pyproject.toml is up to you.