4 ms·

15 year Python dev who usually adopts tooling slowly. Just do it, uv's absolutely worth it. I also use mise with it, which is a great combination and gives yo

15 year Python dev who usually adopts tooling slowly. Just do it, uv's absolutely worth it. I also use mise with it, which is a great combination and gives you automatic venv activation among other things. See, among other mise docs related to Python, https://mise.jdx.dev/mise-cookbook/python.html https://mise.jdx.dev/mise-cookbook/python.html See also a Python project template I maintain built on mise + uv: https://github.com/level12/coppy https://github.com/level12/coppy

NeutralForest 2y ago
I used to install Python through mise but now I just use uv tbh.
- rsyring 2y ago
  Similar. But we get other benefits through mise, like tasks and other tool installs (e.g. Terraform). So we still use them together.
  - NeutralForest 2y ago
    That's fair, it's also nice if you have a backend in Python and a frontend in JS since mise also handles node.
    - rsyring 2y ago
      Forgot about that! Yes, another significant benefit of why we use mise. In particular, we use flask-vite and it's so nice to be able to have the right version of Node specified in the same management system as we specify the Python version. This solved a not insignificant amount of angst around FE development for me personally since I spend most of my time in the BE. It's not like it was insurmountable before. But now, with mise, it's in that "just works" category for me.
      - NeutralForest 2y ago
        100% agreed, it just takes a task that was a 10-15min setup depending on your environment and personal knowledge to a 2min thing. It just makes life easier and it puts the bar for starting lower, a win in my book =)
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 ago
  Mise 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 ago
    the 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

NeutralForest 2y ago

I used to install Python through mise but now I just use uv tbh.

rsyring 2y ago
Similar. But we get other benefits through mise, like tasks and other tool installs (e.g. Terraform). So we still use them together.
- NeutralForest 2y ago
  That's fair, it's also nice if you have a backend in Python and a frontend in JS since mise also handles node.
  - rsyring 2y ago
    Forgot about that! Yes, another significant benefit of why we use mise. In particular, we use flask-vite and it's so nice to be able to have the right version of Node specified in the same management system as we specify the Python version. This solved a not insignificant amount of angst around FE development for me personally since I spend most of my time in the BE. It's not like it was insurmountable before. But now, with mise, it's in that "just works" category for me.
    - NeutralForest 2y ago
      100% agreed, it just takes a task that was a 10-15min setup depending on your environment and personal knowledge to a 2min thing. It just makes life easier and it puts the bar for starting lower, a win in my book =)

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 ago
Mise 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 ago
  the 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