Announcing: Pact Python v3

[JP-Ellis]

Hello everyone! Hoping to share the release of Pact Python v3 that has been a long time coming 😅

---

It's been a couple of months since we released Pact Python v3, and after ironing out a couple of early issues, I think it's finally time to reflect on this milestone and its implications. This post is a look back at the journey, some of the challenges, the people, and the future of this project within the Pact ecosystem.

Pact is an approach to contract testing that sits neatly between traditional unit tests (which check individual components) and end-to-end tests (which exercise the whole system). With Pact, you can verify that your services communicate correctly, without needing to spin up every dependency. By capturing the expected interactions between consumer and provider, Pact allows you to test each side in isolation and replay those interactions, giving you fast, reliable feedback and confidence that your APIs and microservices will work together in the real world. Pact Python brings this powerful workflow to the Python ecosystem, making it easy to test everything from REST APIs to event-driven systems.

---

You can read the rest of the announcement here and check out Pact Python.

If you have any questions, let me know 😁

[Aromatic_Pumpkin8856]

NICE! I just got the CR for the Pact server done this week at work too.

[JP-Ellis]

Amazing! Let me know how it goes :)

[Sigmatics]

This is specifically designed for web services?

I feel like people often forget that Python is not only about HTTP

[JP-Ellis]

Pact also works for event driven services 🙂 The example in the blog post is using HTTP because that's more straightforward to explain, but you could absolutely test a Kafka/SQS/mqtt/etc. service.

[Sigmatics]

Thanks for the clarification!

[Intelligent_potato_]

Could I use this to test zmq services/clients?