OZI.build
This is the OZI-Project maintained fork of the mesonpep517 0.2 tag.
This is a module that implements PEP-517 for the meson build system.
This means that you only need to provide a pyproject.toml and a meson.build in your project source root to be able to create a wheel for the project and to publish your project on PyPI.
Other features include:
signing wheels with JOSE JWS
compiling modules to bytecode with pyc_wheel
scanning pyproject.toml for exploitable ReDoS patterns with regexploit
For more information have a look at the documentation
License
OZI.build is licensed under Apache-2.0 and includes regexploit, pyc_wheel and portions of wheel whose copyright information is reproduced here.
Apache-2.0 contributors
mesonpep517 Copyright (c) 2017-2019 Thibault Saunier <tsaunier@gnome.org>
regexploit Copyright (c) 2021 Ben Caller <REMOVETHISPREFIX.ben@doyensec.com>
pyc_wheel Copyright (c) 2016 Grant Patten <grant@gpatten.com>
pyc_wheel Copyright (c) 2019-2021 Adam Karpierz <adam@karpierz.net>
MIT contributors
wheel Copyright (c) 2012-2014 Daniel Holth <dholth@fastmail.fm> and contributors.
PyJWT Copyright (c) 2015-2022 José Padilla
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
See Also:
Metadata
Release files for OZI.build 2.4.0
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_build-2.4.0.tar.gz | 163.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ozi_build-2.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 280.1 kB
Release files / ozi_build-2.4.0.tar.gz
| Download URL | ozi_build-2.4.0.tar.gz |
|---|---|
| Size | 163.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bdac368307d9fb8ee195a45a924acd2aae8a089274ce6bef4dabf5914f6c7df
|
|
BLAKE2b-256 checksum How to use checksums |
adefeaf3e41f4edfa7b18be53b2a52796d71dd2bbf3474d8e66a9ef9701bc2da
|
| 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 Mar 27, 2026.
Transparency logRelease files / ozi_build-2.4.0-py3-none-any.whl
| Download URL | ozi_build-2.4.0-py3-none-any.whl |
|---|---|
| Size | 116.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
29af5c356e6a751a24cac3524cbbab177453518d6e718a918c9e5fc954ff6b77
|
|
BLAKE2b-256 checksum How to use checksums |
eda9d387b488c1d7d2d2311ea61a7ec2d319883f440f55a613fd1e58b50311a3
|
| 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 Mar 27, 2026.
Transparency log
