pipx

- If it runs Python and pip/pipx, and you can pull in the required packages via pip/pipx, it'll run Reticulum.

Perhaps a case for standardizing on an executable name like `python-script-runner` that will invoke uv, pipx, etc.

Would you be interested in a PR to make a wheel (installable as an application with uv or pipx) from it?

Replacing pipx and `uv run` for single-file scripts with external dependencies, were additional reasons.

For years, pipx did almost all the work that I needed it to do for safely running utility scripts.

CI: I changed a pipeline at work from pip and pipx to uv, it saved 3 minutes on a 7 minute pipeline.

From what I can tell, Hatch, PDM, pipx and pip-run also support it.

Then I lost the project due to a mishap with a pipx flag...

And I’ve yet to hear about pipx or Poetry getting trashed, but if it is a problem, I don’t think it’s impossible to solve in Python vs Rust.

So it's a reasonable complaint that `pip install` has become less useful now that it resists installing tools outside of a venv but still lacks the replacement feature (which third party tools like uv and pipx do provide).

So they follow readme, download windows installer as you say, pip this pipx, pipx that conda, conda this requirements.txt, and five minutes later they have magic error telling that tensorflow version they are installing is not compatible with pytorch version they are installing or some such.

Sometimes it's things like updating to Fedora 43 and every tool you installed with `pipx` breaking because it was doing things that got wiped out by the system upgrade, sometimes it's `poetry update --only dep1` silently updating dep2 in the background without telling you because there was an update available and even though you specified `--only` you were wrong to do that and Poetry knows best.

This isn't really "alternatively"; it's pointing out that in addition to the shebang you can add a PEP 723 dependency specification that `uv run` (like pipx, and some other tools) can take into account.

Right now qlog is a Python CLI, so the cleanest “npm” story is probably a small wrapper package that installs qlog (pipx/uv/pip) and shells out to it, so Node projects can do `npx qlog...` / `import { search } from 'qlog'` without reimplementing the indexer.