Upgrade pact-python from 2.x to 3.x
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
pact-python was pinned to <3 in requirements/constraints.txt because the 3.x release has breaking API changes. The verify_pact.py file uses the 2.x API and needs to be updated to work with pact-python 3.x.
See the pact-python changelog for migration guidance: https://docs.pact.io/implementation_guides/python/changelog
This pin was added as part of dropping Python 3.11 support (https://github.com/openedx/edx-val/pull/597).
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.
Research direction
Read requirements/constraints.txt and inspect the 2.x API usage in verify_pact.py. Follow the pact-python migration guidance in the linked changelog, update the dependency constraint and API usage for 3.x, and confirm the pact verification workflow works with the upgraded version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100