OZI is a set of tools for creating, publishing, and maintaining Python packages using semantic versioning with semantic-release and conventional commits. See the documentation for the project roadmap, API specification, Meson version support, and other project information.
Project Information
Purpose
OZI is meant for Python developers as a standardized and opinionated Python packaging style guide. It consists of command line utilities, a continuous integration checkpointing API using the Meson build system, and continuous deployment scripts.
The OZI continuous integration strategy consists of:
The following isolated checkpoint environments:
code testing and coverage
distributing Python packages with Meson
code linting and formatting
Release drafting
Building and signing of releases
Provenance generation (SLSA v1.0 - Level 3)
Publishing
What OZI is not
A replacement for test environment managers like tox, as a matter of fact OZI uses tox.
A replacement for git hook package management tools like pre-commit
What OZI is
Checkpointed Python packaging for Meson projects focused on pure Python sources.
Contributing
See the project CONTRIBUTING.md
Contact
Eden Ross Duff MSc - help@oziproject.dev
Metadata
Release files for OZI 2.1.31
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ozi-2.1.31.tar.gz | 249.2 kB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| ozi-2.1.31-cp313-none-any.whl | CPython 3.13 | none | any | Details |
| ozi-2.1.31-cp312-none-any.whl | CPython 3.12 | none | any | Details |
| ozi-2.1.31-cp311-none-any.whl | CPython 3.11 | none | any | Details |
| ozi-2.1.31-cp310-none-any.whl | CPython 3.10 | none | any | Details |
Total release size: 366.2 kB
Release files / ozi-2.1.31.tar.gz
| Download URL | ozi-2.1.31.tar.gz |
|---|---|
| Size | 249.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fbdfff1ea59fc2e7ca09aff3de4aefdba9d0f83fc371e88a5855493971f59a75
|
|
BLAKE2b-256 checksum How to use checksums |
64a44ef02d96a789b3a8f567cc35d662f8c145b846b833388481dec237272b7b
|
| 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 Apr 6, 2026.
Transparency logRelease files / ozi-2.1.31-cp313-none-any.whl
| Download URL | ozi-2.1.31-cp313-none-any.whl |
|---|---|
| Size | 30.1 kB |
| Tags | CPython 3.13 |
|
SHA-256 checksum How to use checksums |
1a8723726ffc46942e99ade97e64e89d3277990ef206cd6358feda837eff14ba
|
|
BLAKE2b-256 checksum How to use checksums |
69e94a9ada85ac2af14ea7967c04d99023bb6bf9f4e5cc879db78cad14d630a1
|
| 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 Apr 6, 2026.
Transparency logRelease files / ozi-2.1.31-cp312-none-any.whl
| Download URL | ozi-2.1.31-cp312-none-any.whl |
|---|---|
| Size | 30.1 kB |
| Tags | CPython 3.12 |
|
SHA-256 checksum How to use checksums |
163f35d32347b6d5ec27db9d25d02a41504ef56d5ff18d2e70ad7d0e1edadef4
|
|
BLAKE2b-256 checksum How to use checksums |
83154dac1fc424ed765bdf766765a0f203f7ec638b5b22cf30a57de545e84a4d
|
| 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 Apr 6, 2026.
Transparency logRelease files / ozi-2.1.31-cp311-none-any.whl
| Download URL | ozi-2.1.31-cp311-none-any.whl |
|---|---|
| Size | 31.2 kB |
| Tags | CPython 3.11 |
|
SHA-256 checksum How to use checksums |
7fdc190644ae7d5dcd0266cf87351d992f543f73f123ee20e7f21437040ff3ca
|
|
BLAKE2b-256 checksum How to use checksums |
e957aa24dcb2ab827ca626d41fcfbdcf966a80bc70f5069020208698872716aa
|
| 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 Apr 6, 2026.
Transparency logRelease files / ozi-2.1.31-cp310-none-any.whl
| Download URL | ozi-2.1.31-cp310-none-any.whl |
|---|---|
| Size | 25.5 kB |
| Tags | CPython 3.10 |
|
SHA-256 checksum How to use checksums |
972770c12a0f49c6c67b463ed143fb1dcf212c662da89b00b06d4858c13eb159
|
|
BLAKE2b-256 checksum How to use checksums |
ec9132dd9000d9b839e050f5c49444db4eb81b9e6332fcbb0ba2e10f8ed8a431
|
| 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 Apr 6, 2026.
Transparency log
