onetaskgraph-sdk
The typed Python client for onetaskgraph. Its request vocabulary, response models,
and method surface are generated from the JSON Schema and command help emitted by the
real binary; the workspace's just lint rejects committed output that has drifted.
import asyncio
from onetaskgraph_sdk import Client
tasks = asyncio.run(Client().task_list(status=["todo"]))
Each async call runs one binary subprocess and validates its JSON response. The executable is
resolved in this order: the binary= constructor argument, the
ONETASKGRAPH_SDK_BINARY environment variable, then the onetaskgraph executable supplied
on PATH by the packaged binary distribution. Pass cwd= to select the directory from
which configuration is discovered. Partial query exit status 4 is parsed and returned,
so callers can inspect each typed SourceFailure; other non-zero statuses raise
OnetaskgraphError with the exit code.
Every call also passes --no-interactive, so no call ever waits on a prompt: a template
variable nothing answers takes its default, and a required one left unanswered raises with
exit code 2. template_render(file, search_path=..., answers={...}, var=[...]) hands the
answers mapping to the binary on standard input, and each var (NAME=VALUE) outranks it.
task_create(source, project, title, template=..., answers={...}) and
document_create(...) create an item from a template file — or from
template_loader= (the path of a loader document naming what to render), or from a plain
body= — and answer as task_show and document_show do; the item records its
onetaskgraph.template provenance, which TemplateProvenance reads. task_render(id, ...)
and document_render(id, ...) regenerate one in place from its stored answers, with
answers, var and unset laid over them, and answer with a Regenerated;
task_answers(id) and document_answers(id) answer with the stored TemplateAnswers.
template_variables and template_render take template_loader= in place of a file. A
body and answers are never passed together: both would go to the binary's one standard
input, so the call raises TypeError instead.
1 maintainer
Metadata
1 maintainer
Release files for onetaskgraph-sdk 0.7.2
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 | |
|---|---|---|---|---|
| onetaskgraph_sdk-0.7.2.tar.gz | 120.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| onetaskgraph_sdk-0.7.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 251.8 kB
Release files / onetaskgraph_sdk-0.7.2.tar.gz
| Download URL | onetaskgraph_sdk-0.7.2.tar.gz |
|---|---|
| Size | 120.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d6869db17c487de42326c6cbf21e6e0885722ac8b980cce58324e549fc045673
|
|
BLAKE2b-256 checksum How to use checksums |
08e9e317b261c66e95eaa6030207f3907399565695a75686eecab86f768e4e05
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / onetaskgraph_sdk-0.7.2-py3-none-any.whl
| Download URL | onetaskgraph_sdk-0.7.2-py3-none-any.whl |
|---|---|
| Size | 131.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc31ad951ff4a3ae8084c4cd966bd2851c3e9d196186de42e84a371ab677559e
|
|
BLAKE2b-256 checksum How to use checksums |
c9d1813e71d3c7540a077ef419e9ea92c8864642d85d81303de918a80cff7469
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for onetaskgraph-sdk 0.7.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
