Post v3 tracking issue
Maintainers usually reply within 9 days
@JP-Ellis is already working on this.
Since Oct 6, 2025.
Assessment
This issue has not been assessed yet.
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.
- Dominant language
- Python
- Stars
- 689
- Forks
- 147
- Avg merge
- 8d 11h
- Merged PRs (30d)
- 27
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from pact-foundation/pact-python
-
Function/dict state handlers can't supply provider-state injected values (`generate.provider_state`)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pact-foundation/pact-python#1789 ·
Maintainers usually reply within 9 days
-
area:documentation difficulty:easy type:chore
Difficulty 3/5 1-2 days Newbie friendliness 48/100
pact-foundation/pact-python#1267 ·
Maintainers usually reply within 9 days
-
area:documentation difficulty:easy type:chore
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pact-foundation/pact-python#1266 · 2 comments ·
Maintainers usually reply within 9 days
-
(V3) Verifying a contract with a missing content field is always successful when it should errorPossibly taken @JP-Ellis claimed this 412 days ago. Openarea:core type:bug
pact-foundation/pact-python#1103 · 5 comments · 1 assignee ·
Maintainers usually reply within 9 days
-
Add a complete gRPC examplePossibly taken @JP-Ellis claimed this 514 days ago. Openarea:core area:documentation area:examples difficulty:medium smartbear-supported type:chore
pact-foundation/pact-python#1092 · 1 comment · 1 assignee ·
Maintainers usually reply within 9 days
All issues in pact-foundation/pact-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/datasets#9128 ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenHands/extensions#975 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
juandresrodca/AdminForge#66 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
backend/local comp/tools P2 tool/terminal type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NousResearch/hermes-agent#158788 ·
Maintainers usually reply within 1 day