Trilogy is a batteries-included data-productivity toolkit that accelerates SQL-based analytics with a typed, expressive language. It's great for humans - and even better for agents.
Start with a single file and scale fast with a rich ecosystem, including UI and CLI tooling, public models to get started, rich python integration, and modern visuals and reporting.
Why Trilogy
SQL is the best way to work with data with but shows strain at scale and as it ages. Can we have the pros without the cons? We believe you can.
Trilogy adds a lightweight semantic layer to keep SQL fast through the full lifecycle of analytics - from exploration to production. It provides a full stack for interactive, visualization, and orchestration that can be adopted incrementally and without lock-in; start with checking types and asking agents questions; end with a more efficient and productive warehouse.
Headline features:
- No manual joins; no from clause
- Reusable models, types, and functions
- Safe refactoring across queries
- Supports all standard engines: BigQuery, DuckDB, Snowflake, Presto
- Easy to write - for humans and AI
- Built-in semantic layer without boilerplate or YAML
This repo contains pytrilogy, the reference implementation of the core language and CLI.
Install To try it out, include both the CLI and serve dependencies.
pip install pytrilogy[cli,serve]
or
uv tool install "pytrilogy[cli,serve]"
Docs and Website
Hello World
Trilogy includes a public model registry with prebuilt models to let you get started on the data work fast. Run the below to import, query, and explore one of these models directly.
# 1. Pull a public model (fetches all source .preql files and trilogy.toml).
trilogy public fetch faa ./faa-demo
cd faa-demo
# Run a quick adhoc query (--import prepends the import for you — discover
# what's available with `trilogy explore flight.preql`)
trilogy run --import flight "select carrier.code, count(id) as flight_count order by flight_count desc;"
# Plot it
trilogy run --import flight "chart layer barh ( y_axis <- carrier.name, x_axis <- count(id) as flight_count ) order by flight_count desc limit 10;"
# 3. Add a derived datasource by grabbing the hosted snippet
trilogy file write reporting.preql --from-url https://raw.githubusercontent.com/trilogy-data/trilogy-public-models/refs/heads/main/examples/duckdb/faa/example.preql
# 4. Refresh — builds the managed asset declared in reporting.preql and tracks watermarks.
trilogy refresh reporting.preql
# 5. Launch the Studio UI against the live model (opens your browser) to explore + query
trilogy serve .
trilogy serve . --mcp (install pytrilogy[mcp]) also exposes the model to agents
as an MCP server at http://localhost:8100/mcp, with tools to list models, describe
their fields, read the syntax reference and run queries:
claude mcp add --transport http trilogy http://localhost:8100/mcp
serve binds to localhost by default, where /mcp needs no token (the MCP SDK's
Host/Origin checks guard it). --host 0.0.0.0 exposes the server to the network;
then /mcp requires the printed token as an X-Trilogy-Token header, since queries
can run arbitrary SQL.
The snippet fetched in step 3 looks like this — copy/paste it into your editor if you'd rather author it by hand:
import flight as flight;
# derive reusable concepts
auto flight_date <- flight.dep_time::date;
# this can be properties or metrics
auto flight_count <- count(flight.id);
# datasources can be read from or written to
# use this to write to
datasource daily_airplane_usage (
flight_date,
flight.aircraft.model.name,
flight_count
)
grain(flight_date, flight.aircraft.model.name)
address daily_airplane_usage
;
Browse other available models with trilogy public list (filter with
--engine duckdb or --tag benchmark). Every model in
trilogy-public-models
is pullable.
Principles
Versus SQL, Trilogy aims to:
Keep:
- Correctness
- Accessibility
Improve:
- Simplicity
- Refactoring and maintainability
- Reusability and composability
- Expressivness
Maintain:
- Acceptable performance
Backend Support
| Backend | Status | Notes |
|---|---|---|
| BigQuery | Core | Full support |
| DuckDB | Core | Full support |
| Snowflake | Core | Full support |
| Sqlite | Core | Full support |
| SQL Server | Experimental | Limited testing |
| Presto | Experimental | Limited testing |
Syntax Overview
Trilogy preql models are compositions of types, keys, and properties
Save the following code in a file named hello.preql
# semantic model is abstract from data
type word string; # types can be used to provide expressive metadata tags that propagate through dataflow
key sentence_id int;
property sentence_id.word_one string::word; # comments after a definition
property sentence_id.word_two string::word; # are syntactic sugar for adding
property sentence_id.word_three string::word; # a description to it
# comments in other places are just comments
# define our datasource to bind the model to data
# for most work, you can import something already defined
# testing using query fixtures is a common pattern
datasource word_one(
sentence: sentence_id,
word:word_one
)
grain(sentence_id)
query '''
select 1 as sentence, 'Hello' as word
union all
select 2, 'Bonjour'
''';
datasource word_two(
sentence: sentence_id,
word:word_two
)
grain(sentence_id)
query '''
select 1 as sentence, 'World' as word
union all
select 2 as sentence, 'World'
''';
datasource word_three(
sentence: sentence_id,
word:word_three
)
grain(sentence_id)
query '''
select 1 as sentence, '!' as word
union all
select 2 as sentence, '!'
''';
def concat_with_space(x,y) -> x || ' ' || y;
# an actual select statement
# joins are automatically resolved between the 3 sources
with sentences as
select sentence_id, @concat_with_space(word_one, word_two) || word_three as text;
WHERE
sentences.sentence_id in (1,2)
SELECT
sentences.text
;
Run it:
trilogy run hello.preql duckdb
Python SDK Intro
Use the python SDK to embed Trilogy in larger python workflows.
A BigQuery example, similar to the BigQuery quickstart:
from trilogy import Dialects, Environment
environment = Environment()
environment.parse('''
key name string;
key gender string;
key state string;
key year int;
key yearly_name_count int; int;
datasource usa_names(
name:name,
number:yearly_name_count,
year:year,
gender:gender,
state:state
)
address `bigquery-public-data.usa_names.usa_1910_2013`;
''')
executor = Dialects.BIGQUERY.default_executor(environment=environment)
results = executor.execute_text('''
WHERE
name = 'Elvis'
SELECT
name,
sum(yearly_name_count) -> name_count
ORDER BY
name_count desc
LIMIT 10;
''')
# multiple queries can result from one text batch
for row in results:
# get results for first query
answers = row.fetchall()
for x in answers:
print(x)
LLM Usage
Connect to your favorite provider and generate queries with confidence.
from trilogy import Environment, Dialects
from trilogy.ai import Provider, text_to_query
import os
executor = Dialects.DUCK_DB.default_executor(
environment=Environment(working_path=Path(__file__).parent)
)
api_key = os.environ.get(OPENAI_API_KEY)
if not api_key:
raise ValueError("OPENAI_API_KEY required for gpt generation")
# load a model
executor.parse_file("flight.preql")
# create tables in the DB if needed
executor.execute_file("setup.sql")
# generate a query
query = text_to_query(
executor.environment,
"number of flights by month in 2005",
Provider.OPENAI,
"gpt-5.5",
api_key,
)
# print the generated trilogy query
print(query)
# run it
results = executor.execute_text(query)[-1].fetchall()
assert len(results) == 12
for row in results:
# all monthly flights are between 5000 and 7000
assert row[1] > 5000 and row[1] < 7000, row
CLI Usage
Trilogy can be run through a CLI tool, also named 'trilogy'.
Basic syntax:
trilogy run <cmd or path to trilogy file> <dialect>
With backend options:
trilogy run "key x int; datasource test_source(i:x) grain(x) address test; select x;" duckdb --path <path/to/database>
Format code:
trilogy fmt <path to trilogy file>
Browse and pull public models:
trilogy public list [--engine duckdb] [--tag benchmark]
trilogy public fetch <model-name> [<dir>] [--no-examples]
Fetches model source files, setup scripts, and a ready-to-use trilogy.toml
from trilogy-public-models
into a local directory so you can immediately refresh and serve it.
Managing workspace files from the CLI
trilogy file has shell-agnostic CRUD operations on the filesystem.
trilogy file list . # list entries (-r for recursive, -l for size)
trilogy file read reporting.preql # dump contents to stdout
trilogy file write path --content "..." # create/overwrite from a string
trilogy file write path --from-file src # copy from a local file
trilogy file write path --from-url URL # fetch from http(s):// or file:// URL
trilogy file delete path --recursive # remove a file or directory
trilogy file move old.preql new.preql # rename within a backend
trilogy file exists path # exit 0 if present, 1 otherwise
Backend Configuration
BigQuery:
- Uses applicationdefault authentication (TODO: support arbitrary credential paths)
- In Python, you can pass a custom client
DuckDB:
--path- Optional database file path
Postgres:
--host- Database host--port- Database port--username- Username--password- Password--database- Database name
Snowflake:
--account- Snowflake account--username- Username--password- Password
Config Files
The CLI can pick up default configuration from a config file in the toml format. Detection will be recursive form parent directories of the current working directory, including the current working directory.
This can be used to set
- default engine and arguments
- parallelism for execute for the CLI
- any startup commands to run whenever creating an executor.
# Trilogy Configuration File
# Learn more at: https://github.com/trilogy-data/pytrilogy
[engine]
# Default dialect for execution
dialect = "duck_db"
# Parallelism level for directory execution
# parallelism = 2
# Connection parameters for the dialect; ${env:VAR} reads an environment variable
[engine.config]
# db_location = "local.duckdb"
# Startup scripts to run before execution
[setup]
# startup_trilogy = []
sql = ['setup/setup_dev.sql']
trilogy init [path] [dialect] scaffolds this file, alongside root/ (where
trilogy ingest writes generated models by default), jobs/, and an example
script. Passing a dialect (trilogy init . bigquery) pins engine.dialect and
stubs out that dialect's connection parameters in [engine.config]. Init
refuses to run over an existing trilogy.toml; --force overwrites it and
leaves every other file untouched.
Declared dependencies
Directory runs (trilogy run .) order scripts by what they import, declare
and persist, and a script whose upstream failed is skipped. A [dependencies]
table declares the one kind of edge content cannot express — a script that
runs because another one failed:
[dependencies]
"repair.preql" = { after = ["refresh.preql"], when = "failed" }
when is completed (the default, and the derived-edge rule), failed, or
always. A failed script stands down as a successful skip when its upstreams
held, so the run stays green — and anything downstream of it stands down the
same way, since the script it was waiting on never ran. It runs when one of
them broke, and anything it hands back — a called program printing
::trilogy-output name=fix_pr value=https://… — is listed under Outputs after
the summary and recorded in the --report-file report. Paths are relative to
the toml, and naming a script the run does not manage is an error.
More Resources
- Interactive demo
- Public model repository - Great place for modeling examples
- Full documentation
Python API Integration
Root Imports
Are stable and should be sufficient for executing code from Trilogy as text.
from pytrilogy import Executor, Dialect
Authoring Imports
Are also stable, and should be used for cases which programatically generate Trilogy statements without text inputs or need to process/transform parsed code in more complicated ways.
from pytrilogy.authoring import Concept, Function, ...
Contributing
Clone repository and install requirements.txt and requirements-test.txt.
Please open an issue first to discuss what you would like to change, and then create a PR against that issue.
Similar Projects
Trilogy combines two aspects: a semantic layer and a query language. Examples of both are linked below:
Semantic layers - tools for defining a metadata layer above SQL/warehouse to enable higher level abstractions:
Better SQL has been a popular space. We believe Trilogy takes a different approach than the following, but all are worth checking out. Please open PRs/comment for anything missed!
1 maintainer
Metadata
1 maintainer
Release files for pytrilogy 0.3.404
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 | |
|---|---|---|---|---|
| pytrilogy-0.3.404.tar.gz | 1.8 MB | With provenance | Details |
Built distributions (wheels)
Total release size: 44.5 MB
Release files / pytrilogy-0.3.404.tar.gz
| Download URL | pytrilogy-0.3.404.tar.gz |
|---|---|
| Size | 1.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0198d9f1cdfb5e64064cb81302c2e3e98c7cf70e27e2ac75c76d45269b441bfb
|
|
BLAKE2b-256 checksum How to use checksums |
3ae74445b7feaf070c7fb761f13dd900d8c073d46243ad3f8e911ca7f12dabf1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp314-cp314-pyemscripten_2026_0_wasm32.whl
| Download URL | pytrilogy-0.3.404-cp314-cp314-pyemscripten_2026_0_wasm32.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.14 PyEmscripten 2026.0+ WebAssembly |
|
SHA-256 checksum How to use checksums |
f1ca8181068e665e79ef9ec014654f6cbfb68657dd64eef86a5e7dcf7e05bba0
|
|
BLAKE2b-256 checksum How to use checksums |
beb611eeffdbad720736095c4c28d32db118d12b80d471402aa4e55161eed9f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp313-cp313-win_amd64.whl
| Download URL | pytrilogy-0.3.404-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0e4c05284f79bbe433387837deb4f0a1c9b669d828a9b66266365d1160b4a171
|
|
BLAKE2b-256 checksum How to use checksums |
1468c3a0c10c7e56c419a2073fa37d8abdf3f3c8d9aba64896e3a445c470c34b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pytrilogy-0.3.404-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
43f18a423c95d0a8c3658e8cc0905f3c5db72776480966a10af5174b28633b02
|
|
BLAKE2b-256 checksum How to use checksums |
7726e77409001fe0579f117f73695ad1d46d85d3a82a6730877d300a321c6659
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pytrilogy-0.3.404-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
5dfc9c564db20a7a9c7f94f00d3e687138e65da9ea483bfe6423295a963351f4
|
|
BLAKE2b-256 checksum How to use checksums |
8b861f9ae8adbdad8a8c9b4e9d1b10d27d92b1a098711ef5fdcd40a3c4aa4f56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | pytrilogy-0.3.404-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
355c4229d64003318455c9504ab7dce618e063e2da6ee46605042feceebdc155
|
|
BLAKE2b-256 checksum How to use checksums |
71ab8d35aaa6ede4e1e47c0d377b0b227375f3eac05110a9a6e22a562b19915b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp313-cp313-macosx_10_12_x86_64.whl
| Download URL | pytrilogy-0.3.404-cp313-cp313-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.13 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
266e13fa0d9a0715ad2a90acb0b5864916de6560c8ea2869ba9ed0aca09ef16b
|
|
BLAKE2b-256 checksum How to use checksums |
f7ce58f062fae7f2287f85401fdb5c7e6f1d224edb38b608fc8687583acbc88b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp312-cp312-win_amd64.whl
| Download URL | pytrilogy-0.3.404-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b36bfebf820ecaeeddf11f2b7b286adb61206ad844b3c56baf2c1db48896c6ae
|
|
BLAKE2b-256 checksum How to use checksums |
cc475a45d80e51d896ae6feb41ced2f28973fc86340572655c41aa621b1c3146
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pytrilogy-0.3.404-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
17da7c7496aa08d0ae9656895fe2d0b9ad1c8e5d73dd0cb58f18e0357253f2fa
|
|
BLAKE2b-256 checksum How to use checksums |
a25ab170ef6a21efaacc82e28cedabe6d82876bbcc17dd6fffea2e1a27401e92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pytrilogy-0.3.404-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
db51af9d09d01d998754a4426065a4a4bbe3e1c0413bde063d22d7a99b40f98d
|
|
BLAKE2b-256 checksum How to use checksums |
eb633041b62c75957218989968bfc753723957efcf12c95f5bdfa2bd8cf908f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | pytrilogy-0.3.404-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0df75b6d95a36bd82edb95312472d2a31d820ab2d28ba9c6a4092569c31f3424
|
|
BLAKE2b-256 checksum How to use checksums |
416b6e40b3b142350680739771b8c8bd1e69d372c014296f28e7579768910a26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp312-cp312-macosx_10_12_x86_64.whl
| Download URL | pytrilogy-0.3.404-cp312-cp312-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.12 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
d41721772d4f4cbc2b183c0f912861a0982c22ff49d525b44dce15fd3e5e1831
|
|
BLAKE2b-256 checksum How to use checksums |
fc327453a974aa455890bbfc519ac141b3d6d13744b4c6dcbca67d446b8dd936
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp311-cp311-win_amd64.whl
| Download URL | pytrilogy-0.3.404-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
00432ed3a475c5d81d73ef3839f4bb68d00a751e0e1af92496a91acb1cdcfb9d
|
|
BLAKE2b-256 checksum How to use checksums |
06de0cb74028295e5c5ff163f304c554d66f7610c34193c7ce76ded53cff2f41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pytrilogy-0.3.404-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
46c072f4b2d9ef44f8597e317b87a7e233a9995f80027cf4104a982bff5a92c5
|
|
BLAKE2b-256 checksum How to use checksums |
ee63e174db2f88eb8fa4199f4e13aefbbcf7ec28407a30f321cfe27ba70aaddf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pytrilogy-0.3.404-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
97465d8b1873a5d66697bd6e675cc8775bd943ce85a378d28579ef7c657aed2b
|
|
BLAKE2b-256 checksum How to use checksums |
693b4ac1d550b473324064112e1884533491bd34bd084a4351cfd7af735766d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | pytrilogy-0.3.404-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
95e38006bbf406326f24b0030653e6a1f0ee504c2ae02f1045ef346644926bdb
|
|
BLAKE2b-256 checksum How to use checksums |
02b5b45512ac93c50d9d866994d7b9460035bc0400b24837f8932d122e649e80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logRelease files / pytrilogy-0.3.404-cp311-cp311-macosx_10_12_x86_64.whl
| Download URL | pytrilogy-0.3.404-cp311-cp311-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.11 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
26d1597612753670ccbe2bbdd7d518a50116b0d9ff3c2dd234b1f20be3ded84a
|
|
BLAKE2b-256 checksum How to use checksums |
d571c0477eaf14e999d69d9f86e694b5098c098c7d76a49664990fef536cc4da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 20, 2026.
Transparency logSecurity for pytrilogy 0.3.404
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 17 files in this release have been uploaded with provenance metadata.
Attestation for pytrilogy-0.3.404.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 20, 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.
