render-lab-tasks-braintrust
Unreleased Python port: 12 registered tasks from render-lab/render-tasks. Python 3.12+, Render SDK 1.0.1. Requires core 0.1.1 or later.
From the repository root:
uv sync --all-packages --locked
Import render_lab_tasks_braintrust.tasks to register tasks. The package root is inert.
Compose the exported app with Workflows.from_workflows; call tasks through
ctx.run. Every operation also exports *_impl(ctx, input, *, deps=None) for
injection. Client(http, env) accepts a caller-owned HTTPX client, and
Deps(braintrust=client) injects it. Default dependencies open and close the HTTP
client per invocation; credentials are read lazily at use. No HTTP retries or
background vendor polling occur; retry.py owns the durable retry policies.
Task surface
| Registered task | Python export |
|---|---|
braintrust.addFeedback |
add_feedback |
braintrust.awaitReview |
await_review |
braintrust.deleteDatasetRows |
delete_dataset_rows |
braintrust.ensureDataset |
ensure_dataset |
braintrust.ensureExperiment |
ensure_experiment |
braintrust.gateExperiment |
gate_experiment |
braintrust.getReviewProgress |
get_review_progress |
braintrust.listDatasetRows |
list_dataset_rows |
braintrust.logExperimentResults |
log_experiment_results |
braintrust.runEval |
run_eval |
braintrust.summarizeExperiment |
summarize_experiment |
braintrust.upsertDatasetRows |
upsert_dataset_rows |
Typed JSON inputs and results are in types.py. Task names and JSON field names
match the pinned source; Python function names use snake_case.
Environment
| Variable | Requirement |
|---|---|
BRAINTRUST_API_KEY |
Required at first API call. |
BRAINTRUST_API_URL |
Optional; https://api.braintrust.dev by default. |
Behavior and limits
Stable row IDs are required for upserts and experiment logs. Eval starts and release gates have no retries. Review polling counts rows carrying a score against root-row totals, matching the source; confirm review semantics with nested spans. Dataset pages and experiment summaries reject serialized results at or above 4 MiB. Gate errors contain the violated thresholds. Review polling and result counts remain unverified against a real project.
Verification
All registered tasks have hermetic contract fixtures executed independently against
the pinned TS implementation. SDK-backed tasks also have explicit HTTP request
fixtures. See tests/test_batch3_contracts.py and tests/test_batch3_edges.py.
These are not live vendor results.
Vendor webhooks subpaths and other registration-free TS exports are outside this batch unless explicitly listed above. Full registered-task coverage does not imply all supporting exports are ported.
Pending scopes, test resources, replay, and hosted checks are in the live-testing backlog and verification tracker.
Installation
pip install render-lab-tasks-braintrust==0.1.0
1 maintainer
Metadata
1 maintainer
Release files for render-lab-tasks-braintrust 0.1.0
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 |
|---|---|---|---|---|
| render_lab_tasks_braintrust-0.1.0.tar.gz | 9.3 kB | With provenance | Details for render_lab_tasks_braintrust-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| render_lab_tasks_braintrust-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for render_lab_tasks_braintrust-0.1.0-py3-none-any.whl |
Total release size: 25.8 kB
Release files / render_lab_tasks_braintrust-0.1.0.tar.gz
| Download URL | render_lab_tasks_braintrust-0.1.0.tar.gz |
|---|---|
| Size | 9.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef3d57799b85d2d9a53d720566b918917c96e92839e8d14e2d069c04fbee55a2
|
|
BLAKE2b-256 checksum How to use checksums |
d0cc3316ffa9ab9450c696a77695a290b395f0bfc335e8f701adbc59009037be
|
| 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 Sep 9, 2026.
Transparency logRelease files / render_lab_tasks_braintrust-0.1.0-py3-none-any.whl
| Download URL | render_lab_tasks_braintrust-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
200df2fe62dbf5fa75b0c6ba3c927da980822c9b56b9bb6e089a76707fd5af76
|
|
BLAKE2b-256 checksum How to use checksums |
7057852338594c0c7ce4e891c42d6c63ca5a95dd99d0c24bd1739edc6712af06
|
| 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 Sep 9, 2026.
Transparency logSecurity for render-lab-tasks-braintrust 0.1.0
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 render_lab_tasks_braintrust-0.1.0.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 Sep 9, 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.
