Skip to main content

lmcc — the calling convention for calling a model

When a program calls a function in another language, a calling convention says where each argument goes, how the result comes back, and how each type crosses. A model is another language; lmcc is its calling convention. It lays out each call as an lm15 request and reads each reply back into typed values. It never touches the network.

import lmcc

@lmcc.fn
def answer(question: str) -> str:
    """Answer the question in one sentence."""

xml = lmcc.adapter(messages=[
    lmcc.system("{instruction}\n{% for f in outputs %}<{f.name}>\n{f.value}\n</{f.name}>\n{% endfor %}"),
    lmcc.user("{question}"),
])
plan = answer.bind(xml)
request = plan.render(question="Why is the sky blue?").request("gpt-4.1-mini")   # an lm15 request
plan.read("<Answer>\nRayleigh scattering.\n</Answer>").values   # {'answer': ...}, misspelling repaired and reported

pip install "lmcc[lm15]" adds the typed bridge to lm15 (lmcc_lm15). The tutorial, how-to guides, the normative specification and the conformance corpus are in the repository: https://github.com/MaximeRivest/lmcc

Metadata

Release files for lmcc 0.8.3

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

Source distribution (sdist)

Source distribution for lmcc 0.8.3
File Size Uploaded
lmcc-0.8.3.tar.gz 141.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for lmcc 0.8.3
File Interpreter ABI Platform
lmcc-0.8.3-py3-none-any.whl Python 3 none any Details

Total release size: 251.0 kB

Release files / lmcc-0.8.3.tar.gz

Download URL lmcc-0.8.3.tar.gz
Size 141.7 kB
Tags Source
SHA-256 checksum
How to use checksums
921c61dd1d53ba938ed038fa65b03370590b1c19470913c06ca43185cf8ea4a2
BLAKE2b-256 checksum
How to use checksums
f9ff50736cc6d91933275897868950f592d368194580d5c6cedd8eacd6e8867a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 26, 2026.

Transparency log

Release files / lmcc-0.8.3-py3-none-any.whl

Download URL lmcc-0.8.3-py3-none-any.whl
Size 109.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c55c01ce1872eacd29bd27835c74d05d2fe00ae5c33ba9b2729b56be946958e5
BLAKE2b-256 checksum
How to use checksums
4785228afe9c2b97406bcb98fa9c8d5f4013a038aece680639439f8920689bce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 26, 2026.

Transparency log

Release history Release notifications | RSS feed

0.8.7

2 release files

0.8.6

2 release files

0.8.5

2 release files

0.8.4

2 release files

This release

0.8.3 This release

2 release files

0.8.2

2 release files

0.8.1

2 release files

0.8.0

2 release files

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