Mise, jj (and its phenomenal jjui TUI, which I see you mentioned there), and uv for python are nothing short of revolutionary, as far as I'm concerned. Just beautiful tools.
I never managed to get into mise. I tried, but I think its documentation wasn't good enough for me to be able to configure the things I wanted, and, with uv, I barely ever see a need to use it...
Does anyone have a use case where they use mise with Python? What do you use it for?
Yeah mise and uv are completely complementary - there's no overlap, whatsoever, between them...
In fact, if uv is installed (which can be done via mise), mise uses it for python related stuff.
I use mise to install as much as I can now - different language runtimes, tools/utilities etc. I even discovered yesterday that you can use the ubi backend to install directly from Git repos that aren't yet supported by the other registries.
Mise recently gained support for arbitrary sources too. Things like GitHub, gitlab, or any http URL (with templating). It's got some overlap with ubi, but has a better time with packages that use multiple files, as ubi chokes on anything more than a single binary
Also, it's possible, if trickier, to install from arbitrary git repos.
Finally, if you type `mise use` with no package name, it'll present a filterable list. Start typing what you think you want, and it'll quickly filter to only things match.
mise search <package> will find matches across all the baked in registries, and if its not there you can use ubi, aqua, or any github, gitlab, or http path to get it
Mise, jj (and its phenomenal jjui TUI, which I see you mentioned there), and uv for python are nothing short of revolutionary, as far as I'm concerned. Just beautiful tools.