This is a command line SDK for managing TDM-based dialogue domain descriptions (DDDs). For further information, see talkamatic.se.
Installation
Install the latest version of Tala with pip:
pip3 install tala
CLI
Tala ships a single CLI entry point: tala-interact.
tala-interact https://host/interact/<id>
tala-interact https://host/interact/<id> --ddd my_ddd
Requestor GPT API
GPTRequest in tala.utils.requestor can pass an OpenAI-compatible
response_format to Requestor. For example, strict JSON Schema output can be
requested like this:
from tala.utils.requestor import GPTRequest, GPTStructuredOutputError
request = GPTRequest(
messages=[{"role": "user", "content": "Return the status."}],
model="gpt-6-luna-2026-09-22",
response_format={
"type": "json_schema",
"json_schema": {
"name": "status",
"strict": True,
"schema": {
"type": "object",
"properties": {"status": {"type": "string"}},
"required": ["status"],
"additionalProperties": False,
},
},
},
)
request.make()
try:
result = request.json_response
except GPTStructuredOutputError as error:
print(f"Invalid structured response for request {error.request_id}")
else:
print(result)
print(request.completion_status)
Accessing json_response waits for the request to finish and parses its JSON.
Malformed JSON returned for a structured response raises
GPTStructuredOutputError, which includes the request ID, rather than being
replaced with the default response. completion_status exposes the Requestor
status, such as completed, truncated, refused, incomplete, or error.
For generic JSON-mode requests, allow_json_repair controls the legacy retry
that asks the model to repair invalid JSON. It defaults to True; set it to
False to disable that retry. Structured responses raise
GPTStructuredOutputError for malformed JSON instead of using generic repair.
Metadata
Release files for tala 31.1.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 | Actions |
|---|---|---|---|---|
| tala-31.1.1.tar.gz | 365.9 kB | With provenance | Details for tala-31.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tala-31.1.1-py3-none-any.whl | Python 3 | none | any | Details for tala-31.1.1-py3-none-any.whl |
Total release size: 774.7 kB
Release files / tala-31.1.1.tar.gz
| Download URL | tala-31.1.1.tar.gz |
|---|---|
| Size | 365.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5e29b125955c5752d7478370232a12bf6d559d33ccd1b1565bbf62cc75b9581d
|
|
BLAKE2b-256 checksum How to use checksums |
308059527f16e907ae8198ef153aa8f384bd3013f8ac8e22fa75a1957605415a
|
| 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 30, 2026.
Transparency logRelease files / tala-31.1.1-py3-none-any.whl
| Download URL | tala-31.1.1-py3-none-any.whl |
|---|---|
| Size | 408.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
123d6284368a0b855cb1b1fcdf71645b23be5940f818b19f56c332c4209cbe0d
|
|
BLAKE2b-256 checksum How to use checksums |
61fe4bab3404f426069b528443371206939b0952de346d5dd190b831a6e702f6
|
| 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 30, 2026.
Transparency logSecurity for tala 31.1.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
Both files in this release have been uploaded with provenance metadata.
Attestation for tala-31.1.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 30, 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.