Metadata-Version: 2.4
Name: pipx_isolate
Version: 0.1.1
Summary: a pipx script installer supporting inline metadata for python scripts
Author: purarue
License-Expression: MIT
Project-URL: Homepage, https://github.com/purarue/pipx_isolate
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Programming Language :: Python :: 3.14
Requires-Python: >=3.10
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: click>=8.1.7
Provides-Extra: testing
Requires-Dist: flake8; extra == "testing"
Requires-Dist: mypy; extra == "testing"
Dynamic: license-file

# pipx_isolate

a [`pipx`](https://pipx.pypa.io/latest/installation/) script installer supporting [inline script metadata](https://packaging.python.org/en/latest/specifications/inline-script-metadata/) for python scripts

The purpose for this is to be able to isolate the dependencies for small scripts into a virtual environment.

Inline Script Metadata looks like this:

```python
#!/usr/bin/env python3
# /// script
# requires-python = ">=3.13"
# dependencies = [
#     "beautifulsoup4",
#     "click>=8.3.1",
# ]
# ///

import os
import sys
import contextlib
from typing import Sequence, NamedTuple
import click
from bs4 import BeautifulSoup, Doctype
```

You could either manually add that to your script, or use [`uv`](https://docs.astral.sh/uv/) like: `uv add --script <PATH> click beautifulsoup4`. `pipx_isolate add-metadata <PATH>` shows you all the import statements and wraps `uv add --script`.

Once you have a script that has metadata, you can use `pipx run --path /path/to/script`, which parses the metadata at the top, installs anything that is needed into a venv into `~/.cache/pipx`, and then runs the script in that environment.

Running `pipx_isolate install <name>` looks up the name of the script in your `$PATH`, and creates a wrapper script that looks like this:

```
#!/bin/sh
exec /home/username/.local/bin/pipx run --path /full/path/to/name "$@"
```

This way, if you ever update the metadata at the top, `pipx` picks up the new changes, and runs it with the correct dependencies in a virtual environment.
If you want to pass arguments to `pipx run` in the generated script, you can do so like: `pipx_isolate install <file> --run --no-cache`

`pipx_isolate install` by default creates a `bin` directory at `~/.local/share/pipx_isolate/bin/` so in order to call the wrapper scripts instead of the original, you should update your `$PATH` to put that directory near the front of your `$PATH`:

```bash
export PATH="$HOME/.local/share/pipx_isolate/bin:$PATH"
```

To find/install all the scripts with inline script metadata, I run a command like this:

```bash
rg --files-with-matches -e '/// script' | xargs -I{} sh -c "test -x {} && uv export --script {} --quiet >/dev/null && echo {}" | parallel pipx_isolate install
```

See [`rg`](https://github.com/BurntSushi/ripgrep) and [`parallel`](https://www.gnu.org/software/parallel/)

## Installation

Requires `python3.10+`

To install with pip, run:

```
pip install pipx_isolate
```

## Usage

```
pipx_isolate --help
```

### Tests

```bash
git clone 'https://github.com/purarue/pipx_isolate'
cd ./pipx_isolate
pip install '.[testing]'
flake8 ./pipx_isolate
mypy ./pipx_isolate
```
