Etude
Launch training runs on your own or rented machines, and track what they record.
# job.py
from decimal import Decimal
from etude.jobs import training
from etude.launch.records import Job
from train import TrainConfig, train
def runs() -> Job:
return training(train, config=TrainConfig(lr=1e-3), max_hours=2, max_usd=Decimal(4))
# train.py
from pydantic import BaseModel
from etude.train.records import Step
from etude.train.run import track
class TrainConfig(BaseModel):
lr: float = 3e-4
updates: int = 1000
def train(config: TrainConfig) -> None:
run = track(experiment="capacity-pilot", clocks=[Step("updates", "optimizer updates")])
for update in range(1, config.updates + 1):
loss = train_one_update(config.lr)
run.log({"loss": loss}, updates=update)
if update % 500 == 0:
run.checkpoint(save_model(), updates=update)
run.finish()
etude launch job.py # on this computer; --pool P for machines you own,
# --rent R to rent CPU or GPU machines, or both
etude status # where runs stand
etude logs --run RUN # preparation, every attempt, cleanup
etude reports write --open # charts of every run, as one HTML file per experiment
Etude decides the job's command: on the machine it imports train from your
checkout and calls it with the config, validated back into a TrainConfig. A
config train cannot take is refused before anything launches. An evaluation
job holds a tournament (evaluation) for one checkpoint
the same way, with your play:
from etude.jobs import evaluation
evaluation(progress, play=play, checkpoint=weights, max_hours=0.5, max_usd=Decimal(1))
Everything a run records goes to your own directory or S3 bucket. There is no server to run and no account to make. A run that loses its machine resumes from its last checkpoint on another, and reads back as one run.
Install
Etude needs Python 3.12 and uv.
uv tool install etude-sdk # the `etude` command
uv add etude-sdk # the library, in a training project
uv add 'etude-sdk[s3]' # with S3 or R2 storage
Read more
- Tracking: runs, clocks, checkpoints, reports.
- Evaluation: agents playing each other in parallel, benchmarks and round robins, queried with DuckDB.
- The launcher: typed jobs, pools, SSH hosts, rented machines, cohorts, limits and recovery.
Develop
uv sync
uv run pytest
uv run mypy
uv run ruff check . && uv run ruff format --check .
AGENTS.md holds the conventions, for people and coding agents.
Licence
MIT. See LICENSE.
Metadata
Release files for etude-sdk 0.2.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 | Provenance | |
|---|---|---|---|---|
| etude_sdk-0.2.1.tar.gz | 485.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| etude_sdk-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 836.3 kB
Release files / etude_sdk-0.2.1.tar.gz
| Download URL | etude_sdk-0.2.1.tar.gz |
|---|---|
| Size | 485.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b528350c28a2dcd332a0e254b60bc18448fd7e6aa6f94866beb8bd83930e0d6e
|
|
BLAKE2b-256 checksum How to use checksums |
62c90a8c93fb398d93353418bf3d829a344c2992d448ba192762bf051bccdfbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 24, 2026.
Transparency logRelease files / etude_sdk-0.2.1-py3-none-any.whl
| Download URL | etude_sdk-0.2.1-py3-none-any.whl |
|---|---|
| Size | 351.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
20c16028d78aa82a5785854fd3d7711ead3e702ff95f3cc11accd0776b4ba97c
|
|
BLAKE2b-256 checksum How to use checksums |
9ab0817f47b96dce796b5e8460f72bb5aa67b9b330c71429d4605d912f1f6efa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 24, 2026.
Transparency logSecurity for etude-sdk 0.2.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for etude_sdk-0.2.1.tar.gz
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 Oct 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.