4 ms·
Well, kinda. I haven't used uv, so I'm not sure how strong the dependency (and the lock-in) is. But it looks like just a QoL tool that reads the standard pyproj
by Expurple 1y ago
Well, kinda. I haven't used uv, so I'm not sure how strong the dependency (and the lock-in) is. But it looks like just a QoL tool that reads the standard pyproject.toml, etc. So, it shouldn't be that bad. And if the authors do something weird, you can always stay on an older version, fork it, or switch back to some alternative.
- guappa 1y agoConsidering how python is not very backwards compatibility friendly, that might not be an option.
- Expurple 1y agoI think, this is only relevant for staying on an older version of uv? Which is only a temporary solution, in any ecosystem and in almost any situation. It's just "even more temporary" in Python :) If your old preferred alternative becomes unmaintained in the meantime and starts suffering from the same problems, that's basically equivalent to having to maintain a fork of uv. With the difference that it may be already out-of-date when the uv fork happens