pytest-obligation
Executable contracts for durable work: bind real selection, execution and independent observations to reusable failure/recovery proofs. This directory is the editable library imported by application repositories.
- Adoption guide
- Architecture and guarantees
- Pytest plugin
- Writing bindings
- Interpreting a green result
- Faithful provider fakes
- GitHub Action: evidence, gaps and failures in one PR comment, fork PRs included
- Public applications and demos
The full repository owns demo dependencies, integration tests and release workflows. The library source, controls and maintenance documentation live here.
Local development, package tests and bidirectional subtree sync.
Works with any framework. To bind a Due work-table application, see Due's conformance guide.
1 maintainer
Metadata
1 maintainer
Release files for pytest-obligation 0.21.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 | Provenance | |
|---|---|---|---|---|
| pytest_obligation-0.21.0.tar.gz | 735.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_obligation-0.21.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / pytest_obligation-0.21.0.tar.gz
| Download URL | pytest_obligation-0.21.0.tar.gz |
|---|---|
| Size | 735.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8a4754ec9b8b7c84baa39a9d8e78b68558178d1bee45414798c45b11973fa54
|
|
BLAKE2b-256 checksum How to use checksums |
ff49d2c1e08c8d07aa6942ee2125cae2bcbab8158310ef5e3e4944952acf791f
|
| 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 Oct 25, 2026.
Transparency logRelease files / pytest_obligation-0.21.0-py3-none-any.whl
| Download URL | pytest_obligation-0.21.0-py3-none-any.whl |
|---|---|
| Size | 492.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1680b90e24b688dcfa7f27b83505f6ef421b7d0d1a86fc532f4eaf38702b7c3
|
|
BLAKE2b-256 checksum How to use checksums |
e871de0959edd5ff3318daac377209c6b31971366072c9a13b33a425a03ccb49
|
| 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 Oct 25, 2026.
Transparency logSecurity for pytest-obligation 0.21.0
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.
Attestation for pytest_obligation-0.21.0.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 25, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
