fades

Looking through https://dbohdan.com/scripts-with-dependencies, I see - JS: Deno and Bun - Scala: Scala CLI and Ammonite - Python: fades (https://github.com/PyAr/fades)

I wish an easy cross-platform PEX or shiv [1] were a thing. Binary dependencies are the biggest reason I prefer the new inline script metadata spec (https://packaging.python.org/en/latest/specifications/inline...) and `pipx run`. Luckily, they're pretty great. They have changed how I write Python scripts. The way inline script metadata works is that your script declares arbitrary dependencies in a structured top comment, and a compliant script runner must provide them. Here is an example from a real script: #! /usr/bin/env -S pipx run # /// script # dependencies = [ # "click==8.*", # "Jinja2==3.*", # "tomli==2.*", # ] # requires-python = ">=3.8" # /// pipx implements the spec with cached per-script virtual environments. It will download the dependencies, create a venv for your script, and install the dependencies

There is also fades (https://github.com/PyAr/fades) and pip-run (https://github.com/jaraco/pip-run). Debian and Ubuntu package fades.

You can try https://github.com/jaraco/pip-run or https://github.com/PyAr/fades (or eventually pipx: https://github.com/pypa/pipx/issues/913). They don't require a build step. For example, #! /usr/bin/env -S pip-run Jinja2==3.* from jinja2 import Environment env = Environment(autoescape=True) template = env.from_string("Hello, {{ name }}!") print(template.render(name="world")) There is a downside. Because pip-run recreates the virtualenv every time, the script takes a second to start up. pipx will cache virtualenvs once the single-file script feature is released. I haven't used fades yet. Edit: fades caches virtualenvs. #! /usr/bin/env fades from jinja2 import Environment # fades Jinja2==3.* env = Environment(autoescape=True) template = env.from_string("Hello, {{ name }}!") print(template.render(name="world"))

#!/usr/bin/fades https://github.com/PyAr/fades#what-is-fades

There is the fades utility that installs marked dependencies automatically For example, one could replace a python shebang with fades' one and mark dependencies using # fades comments: #!/usr/bin/fades import dependency # fades https://github.com/PyAr/fades

You should check out fades[0]. It does exactly what you are asking for. [0] https://github.com/PyAr/fades

That's nice. Have you seen fades [0]? It lets you do things like:: fades --requirement requirements.txt myscript.py You can also mark the dependencies in your myscript.py as comments. The use case is for quick one off scripts which may require a bunch of different requirements. The integration with ipython is nice for experimenting too. I think pyenv could be useful for that use case of little one off experiments too. One enhancement I'd like for it to also run modules or entry points like: fades --dependency pygame -m pygame.examples.aliens Setuptools entry points like used in console_scripts to work would be nice too: fades --dependency pyenv -m pyenv.cli:cli Or the best:: fades -m pygame.examples.aliens So it can create a virtualenv, see that it needs the package (pygame here), and then install that package with p

Hello all, We're glad to announce the release of fades 2.0. fades, a FAst DEpendencies for Scripts, is a system that automatically handles the virtualenvs in the simple cases normally found when writing scripts or simple programs. It will automagically create a new virtualenv (or reuse a previous created one), installing the necessary ependencies, and execute your script inside that virtualenv. You only need to execute the script with fades (instead of Python) and also mark the required dependencies. More details here: https://github.com/PyAr/fades/ What's new in this release? - Have a system-wide cache for created virtualenvs: improves reusing and speed - As a result of previous feature, don't store metadata per-script (in the script) anymore - Allow to indicate the project name if the module is different (e.g. "import bs4 # fades.pypi