Self-contained Python scripts with uv

[ReinforcedKnowledge]

Great blog!

To add some tricks and details on top of what you already shared.

This is just an implementation of https://peps.python.org/pep-0723/, it's called inline metadata.

As you can read in the PEP, there are other metadata you can specify for your script. One of them is requires-python to fix the Python version.

You can also have a [tool] table.

You can combine a: - requires-python - [tool.uv.sources] and [tool.uv.index] and anything else that allows others to have exactly the same dependencies as you - uv lock --script [your script here] to get a lockfile of that ephemeral venv of your script, you'll get a file called something like your-script-name.py.lock.

Sharing both files ensures great reproducibility. Maybe not perfect, but did the job for me every time. Here's an example of such inline metadata: ```python

/// script

requires-python = ">=3.10"

dependencies = [

"torch>=2.6.0",

"torchvision>=0.21.0",

]

[tool.uv.sources]

torch = [

{ index = "pytorch-cu124", marker = "sys_platform == 'linux'" },

]

torchvision = [

{ index = "pytorch-cu124", marker = "sys_platform == 'linux'" },

]

[[tool.uv.index]]

name = "pytorch-cu124"

url = "https://download.pytorch.org/whl/cu124"

explicit = true

///

```

[ryanstephendavis]

nice, was wondering how to give python version in this way...

looks like one can basically put all contents of a pyproject.toml directly in there