pip-run

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"))

pipx has merged, though not yet released, support for single-file scripts with dependencies (https://github.com/pypa/pipx/issues/913). There is also pip-run (https://github.com/jaraco/pip-run) with similar functionality to the new feature in pipx and other options. Their approach of listing dependencies in a comment at the top pf the script has been standardized (with minor differences) in a recent PEP: https://peps.python.org/pep-0722/. All of this looks good for the future of Python scripts. I have already adopted pipx run script.py in a project: https://github.com/dbohdan/structured-text-tools/blob/d8dc1a.... It has been convenient and has not caused me problems so far.

> To be recognised as a “comment line”, the line must start with a # symbol. Leading and trailing whitespace on the comment line is ignored. If a line is " # Requirements:" a comment line? I can remove leading whitespace on a comment line, but since it does not start with a "#" symbol, it is not a comment line. In fact, according to this line, there's no such thing as a comment line with leading whitespace. Or is "leading" meant to be the spaces between the "#" and the "Requirements:"? On a broader topic, I certainly haven't followed this issue. I'm curious why an embedded string with a special name wasn't used, like: __pyproject_toml__ = """\ [build-system] requires = ["requests", "rich ~= 58.0"] """ where only '[build-system.requires]' is supported. I think this could be extracted statically, through the AST, so no eval needed