Description
The ask from the community
The README
says you currently support V2 of the spec, please support V3 as well.
Our response
Thank you, we would <3 to see support for v3, and beyond in pact-python. It will involve migrating pact-python from the current ruby based reference implementation (the core), to a rust based reference implementaiton.
We are severely lacking in willing participants, and we are happy to lend a hand in moving things forward <3
If you would love to practise some python and become a pythonista, or you are a seasoned pythonista, drop into #88 and give us a shout!
Current state of play
There has been a few attempts so far at helping tickle along progress of Pact-Python to utilise the new Rust Core.
2 on the verifier side
Examples of python integrating with the FFI
I've put together a demonstration of Python and the Pact FFI based on some of the work done by awesome folk above.
Pact reference
dev rel samples
These are for the consumer side, showing up to v4 Pact's being generated, and utilising the new Pact plugin framework
You can play with it in your browser here
The ask from you
Review the following project tracking is here
https://github.com/pact-foundation/pact-python/projects/1
Get involved!
We would love to find new maintainers or long term contributors to the projects, so would appreciate anyone sharing the word out amongst fellow Pythonista's and see if we can bring this to the masses
Workaround for python provider teams, being provided v3/v4 pacts
You can use the standalone verifier (based on the rust core) as an interim measure
https://docs.pact.io/implementation_guides/cli#native-binary-new
Real Workaround for python provider teams, being provided v3/v4 pacts
- Help review the outstanding PR's
- Fork the project and propose a PR
- Let us know you want to get involved and we can run a hack day
Edits
- Update to provide a coherent response with actionable items at a top level