render-lab-tasks-gmail
Python port of all 16 registered tasks in the pinned TypeScript pack at
45f9c2d44bd28e01ae9813e0d2ff56ee6c533816. Python 3.12+.
Install this distribution and its dependencies:
pip install render-lab-tasks-gmail==0.1.0
Import definitions from render_lab_tasks_gmail.tasks; combine app objects
with Workflows.from_workflows(...). JSON fields retain TS spelling; functions
use snake_case. Package root imports are inert.
Tasks
| Registered name | Python export (also exposes _impl) |
|---|---|
gmail.archive |
archive |
gmail.awaitReply |
await_reply |
gmail.createLabel |
create_label |
gmail.draft |
draft |
gmail.draftReply |
draft_reply |
gmail.forward |
forward |
gmail.getFullThread |
get_full_thread |
gmail.getMessage |
get_message |
gmail.getThread |
get_thread |
gmail.label |
label |
gmail.labelThread |
label_thread |
gmail.listLabels |
list_labels |
gmail.reply |
reply |
gmail.search |
search |
gmail.send |
send |
gmail.trash |
trash |
Dependencies and retries
Raw implementations accept context first and keyword-only deps. The .client
module exports typed Port, Deps, and Client classes. Inject a fake port, or
pass a caller-owned httpx.AsyncClient to Client. Default dependencies close
their client after one operation. Credentials resolve at first use. Transport
retries are disabled; retry.py owns durable policies. DTO types are in .types.
Requires core >=0.1.1.
Environment
| Variable | Contract |
|---|---|
GOOGLE_ACCESS_TOKEN |
Optional pre-issued token; takes precedence. |
GOOGLE_CLIENT_ID |
Required with secret and refresh token when no access token is supplied. |
GOOGLE_CLIENT_SECRET |
OAuth client secret for refresh. |
GOOGLE_REFRESH_TOKEN |
Refresh token granted the scopes for the operations you use. |
Verification and limitations
Reads, labels, drafts, sends, replies, forwards, and reply polling use Gmail v1.
Reply drafts prefer the latest inbound message and preserve MIME threading headers;
optional From must be a verified send-as address. Header CR/LF injection is rejected.
getFullThread defaults to 20 messages and 20,000 UTF-16 units per body; Python drops
a split surrogate pair rather than returning invalid Unicode and rejects invalid
limits. list_labels_impl(ctx, *, deps=...) and wrapped list_labels(ctx) take no
input, matching the TS operation. awaitReply checks one page of ten messages per
attempt; it does not independently verify sender identity. Send/draft/forward
retain retries and may duplicate mail after an ambiguous response. Use test mailboxes.
Shared fixtures execute the actual pinned TS implementations and compare Python outputs and requests. Sanity's SDK calls are translated into separately asserted REST requests. These are hermetic checks, not real account or hosted verification. See the testing backlog and the root verification tracker. Licensed under MIT.
1 maintainer
Metadata
1 maintainer
Release files for render-lab-tasks-gmail 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_gmail-0.1.0.tar.gz | 8.6 kB | With provenance | Details for render_lab_tasks_gmail-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| render_lab_tasks_gmail-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for render_lab_tasks_gmail-0.1.0-py3-none-any.whl |
Total release size: 25.2 kB
Release files / render_lab_tasks_gmail-0.1.0.tar.gz
| Download URL | render_lab_tasks_gmail-0.1.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9d1e18d35fd5df5e01b1cdcc30f642e411cddfa5ce517c078fffc74b8aa40150
|
|
BLAKE2b-256 checksum How to use checksums |
51d5297cc4f7ad678223e1cec9ec4aaa42955e377bdd31d260bcaa6acba00f1d
|
| 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_gmail-0.1.0-py3-none-any.whl
| Download URL | render_lab_tasks_gmail-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b208a7f1ebf4086a64c75c59086f839ec39f01f5f33791d7a9267c39e418739
|
|
BLAKE2b-256 checksum How to use checksums |
587c69317648b6895aba4da10d38491401ed637d04f258bdfb9be0084e7f8f15
|
| 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-gmail 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_gmail-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.
