Hey, team I raise an issue for pact-python because the pact binaries(version 1.88.83) combined in pact-python is incompatible with dev env and CI pipeline. I always got the same error response when I try to verify my pact. But when I use the latest binaries version(1.91.0). The issue won't exist. So are we going to upgrade the version combined in pact-python or is there a suitable way I can config the version that pact-python will call? That's will be much helpful for my implementation. Thanks!

I’ve just opened a PR to update the standalone to 1.91.0

sdist

is the step that attempts to download the binary https://github.com/pact-foundation/pact-python/blob/d87d54bce2ed2f74b0a2bb46314b18541bdb598a/setup.py#L30

I think

sdist

tried to download a linux-x86.tar.gz binary package and at the 1.91.0 version we don't own this type of binary package at all which failed the build https://github.com/pact-foundation/pact-python/blob/d87d54bce2ed2f74b0a2bb46314b18541bdb598a/setup.py#L21

Yep I think so too: https://github.com/pact-foundation/pact-python/actions/runs/3531375062

I think pact-python have packaged all the operating systems binaries and choose the suitable one during the test run. So checking all operating systems during the build seems persuasive. But I don't know why the 3.10 test failed(seems ruby issue) and I don't have much background why later version binary abandoned the linux-x86.tar.gz type🫠

support was dropped for one of the old linuxes, but I don’t know why python would care about that. it should be agnostic to the name of the package.

It cares about it because it pulls the package down during the build/install step

ah, right, I think that distribution needs to be removed from the code

yep