Support/workflows for editable packages (with Python and pipx)?

[proceduralnoisy]

Our use case seems like a perfect fit for mise: A Python-based CLI tool (let's call it 'mytool') that is used by build processes in local and CI workflows. Different code repositories may use different versions of 'mytool', and multiple repositories may appear on the same machine.

Mise works great here - we can simply place a .mise.toml file in each repository, specifying the desired version of 'mytool' as follows:

[tools]
"pipx:mytool" = {version = "1.2.3"}

This works for published versions of mytool, but we would also like the ability to point to a local editable clone of 'mytool' for debugging/development of the 'mytool' tool itself.

Does mise support pipx/pip/uv 'editable' packages?

Without mise, we would run pipx install mytool --editable /path/to/mytool/repo, so I was hoping something like this would work via mise:

[tools]
"pipx:mytool" = {version = "local", pipx_args = "--editable /path/to/mytool/repo" }

Unfortunately, that doesn't work (it yields pipx install mytool==local --editable /path/to/mytool/repo, but pipx doesn't want a package name/version for editable packages).

I suppose we could handle this outside mise by using pipx directly to install the editable package globally, and then using a .mise.local.toml file with "pipx:mytool" = "system" in the mise.toml file, but it would certainly be nice if there was a mise-integrated solution here.

Thanks!