6 ms·
ideally mise could be replaced entirely by uv or at least just be a thin wrapper around uv (in some ways that's already the case), but given this article requir
by jdxcode 2y ago
ideally mise could be replaced entirely by uv or at least just be a thin wrapper around uv (in some ways that's already the case), but given this article requires the use of the custom uv-python-symlink utility it seems uv isn't quite there yet
- rsyring 2y agoMise does way more than uv, it's a much larger scope than just Python tooling. I think the current status quo, that of mise utilizing uv for it's Python integration support, makes sense and I don't see that changing. Also, FWIW, mise has other methods for Python integration support, e.g. pyenv, virtualenv, etc. Edit: Ha... Didn't realize who I was replying to. Don't need me to tell you anything about mise. I apparently misinterpreted your comment.
- jdxcode 2y agothe reality that I'm sure you've heard me say many times is that I'm just not a python dev and astral is likely always going to build a better solution around python than I ever could. They've just focused a lot more on the package manager side of things than the runtime/venv management side so far but I suspect that will change—and given astral's velocity I doubt we'll be waiting long and btw mise's venv support isn't going anywhere probably ever, but I do hope that at some point we could either let uv do the heavy lifting internally or point users to uv as a better solution