Feature Request: Expose `Python.Uv.run!`

[wingyplus]

I am trying to integrate a Python tool that requires running a Python binary, and see that Python.Uv has a run function that automatically downloads the uv binary if it is not available. So I propose to expose the Python.Uv.run! function so the user can execute any Python binary that is defined within the pyproject.toml.

[jonatanklosko]

Hey @wingyplus!

execute any Python binary that is defined within the pyproject.toml.

Do you mean python executable, or a Python script? Could you provide a simple example?

[wingyplus]

Sorry for the late reply.

My usecase is that I have a dbt project that call by the Elixir library. What I need is to run it via a uv binary.

I try to install the uv binary by itself but I see that this library has a way to run any command with uv (and auto installation support).

That’s the reason why I request to expose a function.

[jonatanklosko]

To clarify, do you mean uv run python script.py? Does the script return anything?

Perhaps for your use case you could Pythonx.eval, this code:

import subprocess
import sys

subprocess.run([sys.executable, script_path])

You could also only get sys.executable from the eval, and then run it from Elixir.

A convenience API we could consider is something like Pythonx.run_script, which would not be tied to uv.

Sidenote: currently, when deploying, uv is only used at compile time and it is not even packaged into the release.

[nerdyworm]

My usecase, I would like to, from elixir shell out to a uv run myscript_in_priv.py It wouldn't need to return data to elixir (would be cool, but not needed).

Generally i run into two little problems. One off scripts that are very crashy that i don't want running in my vm and then port programs that have long running servers.

This library provides a delightful experience for including python/uv into our codebase. We'd like to keep that workflow if possible :)

I hope this makes sense.