pact-foundation / pact-foundation/pact-python
Post v3 tracking issue
Open
@JP-Ellis is already working on this.
Since Oct 6, 2025.
type:tracking
- Dominant language
- Python
- Stars
- 684
- Forks
- 147
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 12
Description
Pact Python v3 is a major rewrite, introducing a new Rust-based core for improved performance, feature parity, and maintainability. As with any major change, while the hope is for a smooth transition, this ticket will help track new issues and/or questions from the change, as well as any outstanding work.
The Pact Python documentation is available at pact-foundation.github.io/pact-python. In particular:
- If you have an existing codebase, I recommend you read through the migration guide
- The consumer and provider docs have been entirely re-written to feature Pact Python v3
- There are some end-to-end examples, with more coming soon.
What to do if you have an issue with v3
- Check the list below to see if your issue is already tracked.
- Review the migration guide and documentation for breaking changes and usage updates.
- Open a new issue if your problem is not listed, providing as much detail as possible (version, OS, code sample, error output).
Documentation & Example Improvements
- #372
- #377
- #1092
- #1266
- #1267
- #1274
- #1302
Features & Enhancements
- #1005
- #731
- #451
- #326
Bugs & Issues
- #1103
- #1069
- #1275
Thank you for helping improve Pact Python v3!
Please use this issue to discuss migration, report bugs, and track progress on post-v3 tasks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.