Pact Python
Fast, easy and reliable testing for your APIs and microservices.
| Package |
|
| CI/CD |
|
| Meta |
|
| Community |
|
Pact is the de-facto API contract testing tool. Replace expensive and brittle end-to-end integration tests with fast, reliable and easy to debug unit tests.
Why use Pact? Contract testing with Pact lets you:
Watch our series on the problems with end-to-end integrated tests, and how contract testing can help. |
Documentation
This readme provides a high-level overview of the Pact Python library. For detailed documentation, please refer to the full Pact Python documentation. For a more general overview of Pact and the rest of the ecosystem, please refer to the Pact documentation.
Documentation for the API is generated from the docstrings in the code which you can view at pact-foundation.github.io/pact-python/pact.
Need Help
- Join our community slack workspace.
- Stack Overflow is a great place to ask questions.
- Say 👋 on Twitter: @pact_up
- Join a discussion 💬 on GitHub Discussions
- Raise an issue on GitHub
Installation
The latest version of Pact Python can be installed from PyPi:
pip install pact-python
# 🚀 now write some tests!
Requirements
Pact Python tries to support all versions of Python that are still supported by the Python Software Foundation. Older version of Python may work, but are not officially supported.
In order to support the broadest range of use cases, Pact Python tries to impose the least restrictions on the versions of libraries that it uses.
Telemetry
In order to get better statistics as to who is using Pact, we collect some anonymous telemetry. The only things we record are your type of OS, and the version information for the package. No personally identifiable information is sent as part of this request. You can disable telemetry by setting the environment variable PACT_DO_NOT_TRACK=1:
Contributing
We welcome contributions to the Pact Python library in many forms. There are many ways to help, from writing code, to providing new examples, to writing documentation, to testing the library and providing feedback. For more information, see the contributing guide.
2 maintainers
Metadata
2 maintainers
Release files for pact-python 4.2.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 | Actions |
|---|---|---|---|---|
| pact_python-4.2.0.tar.gz | 74.2 kB | With provenance | Details for pact_python-4.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pact_python-4.2.0-py3-none-any.whl | Python 3 | none | any | Details for pact_python-4.2.0-py3-none-any.whl |
Total release size: 157.5 kB
Release files / pact_python-4.2.0.tar.gz
| Download URL | pact_python-4.2.0.tar.gz |
|---|---|
| Size | 74.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2940d8895421b10576e04b6f1a19a815d81be68b9f777a92c1014426c70d234f
|
|
BLAKE2b-256 checksum How to use checksums |
2da0eeddea8954ad6307045332874f2da6555cb86c6f2bfb25c6bfbbbd8a26c3
|
| 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 23, 2026.
Transparency logRelease files / pact_python-4.2.0-py3-none-any.whl
| Download URL | pact_python-4.2.0-py3-none-any.whl |
|---|---|
| Size | 83.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
99bf0e5fbf6211a46bb0b362282fbdd09da4b59106b3ad02d10232f716f24965
|
|
BLAKE2b-256 checksum How to use checksums |
b692bf6924265422c442c6767a9965a157954b49c4233275a6f61d387123db4f
|
| 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 23, 2026.
Transparency logSecurity for pact-python 4.2.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 pact_python-4.2.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 23, 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.
