Warning lote is early (
0.0.x). The config and commands may still change.
Installation
pip install lote # the lote command, ready to use
chefe add lote --pypi # or pull it into a chefe project
The command is lote. It drives each host through chefe, which lote setup installs for you and which brings up pixi on first run.
What it is
You have a laptop and a handful of machines, each one running a different scheduler and expecting a different incantation. lote is one bridge over all of them. You pick a host, lote rsyncs your repo there, runs your job under whatever scheduler that host has (pueue, slurm, pbs, or bare bash), and pulls the results back. One job script runs anywhere, no code changes.
It works in three layers. The control plane lote onboards hosts, dispatches jobs, and tracks them across your machines. The on-host executor lote exec runs, submits, and monitors a single job on one machine. Underneath are typed clients over qsub, sbatch, pueue, and rsync. Targets come from your ~/.ssh/config aliases, so there is nothing new to declare.
Usage
lote setup dgx # onboard: probe, sync, install the env, start the queue
lote run dgx "python train.py" # queue the command, stream its output, exit with its code
lote run dgx "python train.py" --detach # same, but return a handle and survive disconnect
lote submit dgx train.sh # ship the repo, launch the job, get a handle back
lote submit auto train.sh --needs 40 # or route to the smallest host that fits
lote ps dgx # one host's live jobs (any scheduler), uniformly
lote logs dgx <handle> # the captured output of any run, even after it ends
lote cancel dgx <handle> # stop a job on any backend (kill is an alias)
lote ps # recent runs across every target
lote pull <handle> # rsync the run's results back home
Tip
lote runandlote submitdispatch through the same scheduler, sops,logs, andcancelwork the same way on a laptop, a bare ssh host, or a PBS/SLURM cluster.lote reconcile <target>shows each run's live state, exit code, and a verdict (ok, failed, running, vanished). The docs cover the full command set.
Lore
A lote is a load shipped as one consignment. lote ships your work the same way: pick a machine, send the job, bring the results home.
Metadata
Release files for lote 0.0.3
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 | Actions |
|---|---|---|---|---|
| lote-0.0.3.tar.gz | 341.3 kB | With provenance | Details for lote-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lote-0.0.3-py3-none-any.whl | Python 3 | none | any | Details for lote-0.0.3-py3-none-any.whl |
Total release size: 466.3 kB
Release files / lote-0.0.3.tar.gz
| Download URL | lote-0.0.3.tar.gz |
|---|---|
| Size | 341.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78ab493b5ee59778edc24aa4643f7839c6f6371f61e6a60c5f5245b0d20f77d8
|
|
BLAKE2b-256 checksum How to use checksums |
35d920ea6d541a8856324d5bdab29d995ce19a5cf143fdba4d7786c7f82da9a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 6, 2026.
Transparency logRelease files / lote-0.0.3-py3-none-any.whl
| Download URL | lote-0.0.3-py3-none-any.whl |
|---|---|
| Size | 124.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9336bda15d501dfbdfcbe2d8f880138db604ddbaa238fdf64a850b8ca31b62cc
|
|
BLAKE2b-256 checksum How to use checksums |
8622d960fd6e40fec7778a143c755a0c912ae14103ccd4d32b275ec779d064d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 6, 2026.
Transparency logSecurity for lote 0.0.3
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 lote-0.0.3.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 Aug 6, 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.