I was just looking at https://github.com/wiremock/python-wiremock/pull/48. What about dropping the JAR file that is bundled on the Python package completely, and documenting how the user should download the JAR and use it with the

jar_path

argument?

Maybe? Cc @mike waites Personally I just want to have Testcontainers integration in place so that we forget about JARs for good

we use wiremock with behave (https://behave.readthedocs.io/en/latest/), from there we drive wiremock using wiremock-python. We run wiremock as a container using the official docker image. In fact, we run all our integration tests using containers with docker-compose