Using the UV hashbang and a few doc strings for dependencies so you can run full on python scripts as executables is fucking crack.
I have an idea of what this might look like, but do you have any examples I can crib from?
This article looks like it explains the process:
https://mathspp.com/blog/til/standalone-executable-python-scripts-with-uv
Thank you, this goes to the top of my reading pile for tomorrow! We’ve been doing a lot of uv conversions at work and I have a specific personal use for this as well
And it isn’t even written in Python!
This page said it’s written in Rust. Is this the same UV?
That means it can’t be maintained by the community it’s serving. For those skilled in both Rust and Python can understand why it would appear as the best thing since sliced bread.
What about for those not skilled in Rust? Should we also learn 15 other coding languages while we are at it?
wreck is written in Python and manages dependencies. via hierarchy of requirements files, not TOML. It’s venv aware. For Python package authors.
Does it allow differentiating between dependencies and dev dependencies though? I couldn’t gather that from the article.
wreck can. It’s venv aware. Takes full advantage of hierarchical requirement files. Is intuitive. The learning curve is minimal. Written in Python.
[[tool.wreck.venvs]] venv_base_path = '.venv' reqs = [ 'requirements/pip', 'requirements/pip-tools', 'requirements/prod', 'requirements/dev', 'requirements/manage', 'requirements/kit', 'requirements/mypy', 'requirements/tox', ] [[tool.wreck.venvs]] venv_base_path = '.doc/.venv' reqs = [ 'docs/requirements', 'docs/pip-tools', ][tool.setuptools.dynamic] dependencies = { file = ['requirements/prod.unlock'] } optional-dependencies.pip = { file = ['requirements/pip.lock'] } optional-dependencies.pip_tools = { file = ['requirements/pip-tools.lock'] } optional-dependencies.dev = { file = ['requirements/dev.lock'] } optional-dependencies.manage = { file = ['requirements/manage.lock'] } optional-dependencies.docs = { file = ['docs/requirements.lock'] }reqs fix --venv-relpath='.venv'reqs fix --venv-relpath='.doc/.venv'From
*.inrequirements files would produce*.unlockand*.lockfiles for venv.venv. Package versions are sync’ed within all requirements files within that venv.
They kind of lost me at piping a script to sh. Is this the official way? Get your shit packaged into the popular distros. DevOps isn’t that hard.
example of using uv to install a python tool:
uv tool install harlequinnice! It just works (harlequin.sh is a python program that allows to interact with databases using SQL qury langues, you can also load csv and json data)
I know it’s not the point of this comment, but I’ll check harlequin out
