Skip to main content

Malloy Publisher Python SDK

Auto-generated, fully typed Python client for the Malloy Publisher REST API.


Installation

pip install malloy-publisher-sdk  # once published on PyPI

For local development against the monorepo:

cd packages/python-client
uv venv .venv        # create virtual env (requires `uv`)
source .venv/bin/activate
uv pip install -e ".[test]"  # editable install with test extras

Quick-start

from malloy_publisher_sdk import Client, errors
from malloy_publisher_sdk.api.environments import list_environments

client = Client(base_url="http://localhost:4000/api/v0")

try:
    environments = list_environments.sync(client=client)
    for env in environments:
        print(env.name, env.resource)
except errors.ApiError as exc:
    print(exc.status_code, exc.body)

Async usage

import asyncio
from malloy_publisher_sdk import Client
from malloy_publisher_sdk.api.environments import list_environments

async def main():
    async with Client(base_url="http://localhost:4000/api/v0") as client:
        environments = await list_environments.asyncio(client=client)
        print([e.name for e in environments])

asyncio.run(main())

Development

Regenerating the SDK

When the OpenAPI spec (api-doc.yaml) changes, run the helper script and commit the diff:

cd packages/python-client
scripts/build-python-sdk.sh

The script performs:

  1. Spec validation
  2. Code generation via openapi-python-client
  3. Version synchronization
  4. Formatting, linting, type-checking
  5. Test execution

Building the Package

To build the Python package for distribution:

# Build only (for testing)
./scripts/build-package.sh

# Or build as part of SDK generation
BUILD_PACKAGE=true ./scripts/build-python-sdk.sh

This creates wheel and source distributions in the dist/ directory.

Version Management

The package version is managed in pyproject.toml. Update the version there and run the build script to synchronize it across all files.


Contributing

Pull requests welcome! Make sure ./scripts/build-python-sdk.sh passes before opening a PR.

For packaging changes, also verify:

./scripts/build-package.sh  # Test package building
pip install dist/*.whl      # Test local installation

License

MIT © Malloy Data

Metadata

Release files for malloy-publisher-sdk 0.11.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for malloy-publisher-sdk 0.11.2
File Size Uploaded Provenance Actions
malloy_publisher_sdk-0.11.2.tar.gz 193.3 kB With provenance Details for malloy_publisher_sdk-0.11.2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for malloy-publisher-sdk 0.11.2
File Interpreter ABI Platform Actions
malloy_publisher_sdk-0.11.2-py3-none-any.whl Python 3 none any Details for malloy_publisher_sdk-0.11.2-py3-none-any.whl

Total release size: 618.8 kB

Release files / malloy_publisher_sdk-0.11.2.tar.gz

Download URL malloy_publisher_sdk-0.11.2.tar.gz
Size 193.3 kB
Tags Source
SHA-256 checksum
How to use checksums
15fabf5ca979e849d7a186ff9be1c88b07914fc43ba25826560a2d5eb48817f7
BLAKE2b-256 checksum
How to use checksums
df70fcda6c9e7f717b0904859fe3f4ee5d50ef0664291cbeca6dd3f33357e2b5
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 Nov 3, 2026.

Transparency log

Release files / malloy_publisher_sdk-0.11.2-py3-none-any.whl

Download URL malloy_publisher_sdk-0.11.2-py3-none-any.whl
Size 425.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
464ad1893b1f07992d38261e90d2a900b874bca924eb213d0df5a0f17889882c
BLAKE2b-256 checksum
How to use checksums
aea41822e0a069dc070dd1a1720535e0dcbab3e5d63eb0f8db187c705c64507b
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 Nov 3, 2026.

Transparency log

Security for malloy-publisher-sdk 0.11.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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for malloy_publisher_sdk-0.11.2.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 Nov 3, 2026.

Transparency log

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page