wend
A library for templated paths using Python t-strings (3.14+)
Installation
uv pip install wend
Requirements
- Python 3.14+
About
For backstory read my blog about this package cog.spin.systems/future-paths!
The general idea is to use t-strings to house eagerly instantiated parameter objects which offer a form of deferred execution.
Usage
Following the examples in the blog post:
from pathlib import Path
from wend import Param, P, T, RelativePath
# Define parameters (late-bound)
root = Param("root")
dataset = Param("dataset")
idx = Param("idx")
total = Param("total")
# Build expressions - these don't touch the filesystem
data_dir = root / "data" / dataset
chunk_file = data_dir / T(t"chunk_{idx:04d}-of-{total:04d}.parquet")
# Inspect what's needed
print("Required params:", chunk_file.required_params())
# -> {'root', 'dataset', 'idx', 'total'}
# Resolve with bindings
path = chunk_file.resolve({
"root": "/mnt/storage",
"dataset": "train",
"idx": 7,
"total": 100,
})
print("Resolved:", path)
# -> /mnt/storage/data/train/chunk_0007-of-0100.parquet
# Constant folding happens at construction
folded = P("/home") / "user" / "data"
print("Folded type:", type(folded).__name__)
# -> LiteralExpr (not nested JoinExprs)
# Parent simplification
expr = root / "a" / "b"
print("Parent of join:", expr.parent)
# -> JoinExpr(ParamExpr, LiteralExpr("a")) -- the "b" is gone structurally
# Suffix chain collapse
double_suffix = (root / "file.txt").with_suffix(".tmp").with_suffix(".json")
print("Suffix chain:", double_suffix)
# -> WithSuffixExpr(base=JoinExpr(...), suffix='.json') -- .tmp is gone
# Connectivity: rebasing
config = RelativePath(
base=root,
relative=P("config") / "settings.yaml"
)
print("Config path:", config.resolve({"root": "/project"}))
# -> /project/config/settings.yaml
# Rebase to test environment
test_config = config.rebase(P("/tmp/test"))
print("Test config:", test_config.resolve({}))
# -> /tmp/test/config/settings.yaml
Contributing
Contributions are welcome! Please:
- Open an issue to discuss bugs or feature requests
- Fork the repo and submit a PR for changes
- Install dev dependencies with
uv syncand runpre-commit install
License
MIT License - see LICENSE for details.
Metadata
Release files for wend 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| wend-0.1.1.tar.gz | 4.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wend-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.9 kB
Release files / wend-0.1.1.tar.gz
| Download URL | wend-0.1.1.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
98ffc45961f783d697b53eb39c905011c50822424531fc00b2e75c6f0eff542a
|
|
BLAKE2b-256 checksum How to use checksums |
9aacfa914cf2d5504d4f62e04e874216802d9555f0c4b5eab4664057c6ea7717
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 3, 2026.
Transparency logRelease files / wend-0.1.1-py3-none-any.whl
| Download URL | wend-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ca6d8f858a3490580f20dec73510934ca272e81adf58b0ee078ddccde47b989e
|
|
BLAKE2b-256 checksum How to use checksums |
fad747220a06f4935f9b10081f15cd36b876e808c7be4efaf6ff403277b013fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 3, 2026.
Transparency log