Feature Request: Expose `Python.Uv.run!`
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
Research direction
Start by reading the existing Python.Uv.run entry point and the issue's description of binaries defined in pyproject.toml. The work is complete when Python.Uv.run! is exposed so users can execute those Python binaries through the public API; the payload names no files or tests to run.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Elixir
- Stars
- 316
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from livebook-dev/pythonx
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
livebook-dev/pythonx#49 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
livebook-dev/pythonx#40 · 1 comment ·
All issues in livebook-dev/pythonx
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
phoenixframework/phoenix#6847 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
moderation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
beyond-all-reason/teiserver#1584 · 1 comment ·