scripts: added inline script metadata per PEP 723 #11597
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
In October 2023, PEP 723 introduced an official specification for inline script metadata: https://packaging.python.org/en/latest/specifications/inline-script-metadata/
Inline script metadata allows compatible tools to discover the dependencies of a given script without needing to parse any
requirements.txt
orpyproject.toml
.For example, the
uv
tool supports this, which means you can just runuv run ./script.py
and it will automatically parse the metadata and create a temporary virtual environment.Because inline metadata is just a comment, it's fully backwards-compatible; tools that don't use it will just ignore it.
Changes
This PR adds inline metadata to the Python scripts in the
scripts/
directory, such that they can be directly run with compatible tools.Example (note that I wasn't in a virtual environment and my global Python packages remained untouched):