Randy Syring

Maybe the real issue here is that virtualenv management should be separated from the Python tool and a different plugin/tool dedicated to virtualenv management could be created? There could then...

I've experienced this myself and it's due to the Python virtualenv being created. Given you are using python virtualenvs I'd bet that's it. I've thought there should be better UX...

Per #690 - the time it takes to create the virtualenv is significant from a UX perspective. Should at least let the user know what is happening: "Creating Python virtualenv...

FWIW, I just ran into this after an rtx -> mise migration because I didn't have the Python version installed that the project called for. I was using `which python`...

I think all the work you are doing on this, as well as your desire to make mise as friendly as possible, is commendable. For whatever its worth, I found...

@dnicolson I believe: * Warnings about missing tools are hidden by default with mise * Using `mise activate --status --log-level=warn` will give you the warnings So, assuming "both lines in...

I've been working around this with: ```toml [env] # ...snip... [tools] python.version = '3.9.1' python.virtualenv='{{env.WORKON_HOME}}/twt' ``` I'm not sure if the explicit use of the variable ends up being a...

I guess I thought `env` was mostly for environment variables. So putting what are essentially tool configuration/settings in the environment section seems weird to me. But mise is already way...

> so a lot of people are saying that to me :) > I think venvs are just env vars with some side effects My guess is that this is...

> keep in mind I'm trying to get out of managing the virtualenv. FWIW, that was the conclusion I came to based on the issues I've been a part of...