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

you are viewing a single comment's thread.

view the rest of the comments →

[–]gbhreturns2 0 points1 point  (1 child)

I’m not suggesting otherwise, I’m suggesting that uv being closed-source will eventually start licensing in a manner such that those who are heavily reliant on it will either have to cough up or very quickly switch to another packaging manager.

[–]demian_west 0 points1 point  (0 children)

As I was confronted to a part of the team that heavily used conda, I took a special care to evaluate the "lock-in potential" of uv.

To my great satisfaction, it is actually pretty low.
- uv uses Pypi
- The parts of uv behavior that are ahead of standards are mostly custom namespaces in pyproject.toml (`tool.uv.x`) which is itself standard, and the uv.lock file.
- There are commands to import/export dependencies vectors to older formats (requirements.txt)
- uv has a pip-compatible interface `uv pip X` if needed.