How to tell mise to some python packages without using a venv or global ~/.default-python-packages?

[ssbarnea]

I do want to install some python packages like uv and tox but without making use of the global option ~/.default-python-packages because this one cannot be configured inside the repository and it does affect other tools.

I know that the first suggestion would be to make use of venv but for some projects this would be an overkill.

Is there another way to tell mise to use a python version end ensure that a list of pip dependencies are also installed? -- Please note that I do not want to run another command to do this manually.

To better explain myself, I use tox to test over 95% python projects and tox takes care of virtualenv management itself. Still, installing tox on a new machine (CI too) would require additional steps, so it would be much better if I can just test mise to take care of this and only mention mise as a required build tool, reducing the number of steps require to prepare the development/testing environment.

Apparently the https://mise.jdx.dev/lang/python.html#default-python-packages option is one of the few that does not have a mise.toml configuration option and can only be controlled via MISE_PYTHON_DEFAULT_PACKAGES_FILE,.. not really sure why.

Update: I also observed that if I modify the .default-python-packages file mise to add something to it, mise will not know to install the missing tools and using the mise install python --force would force full download of the entire python. Apparently no middle ground for updating these dependencies.

[syhol]

You're not the first to want this behavior. Others have solved it by using a postinstall hook to call something like uv pip install -r tools.txt. You don't need to call any other commands and it will run on a mise install.

You could also do it on an enter hook, but that requires mise to be activated. Also it will run each time you enter the directory, not just the first time, so that could get annoying after a while.