set the channel description: A channel for those using WireMock with Python. Development, tools, etc.

👋 @mike waites

And 👋 @Cody Lee

👍

FYI @Cody Lee @mike waites you should have maintainer permissions in the repository now. I enabled better security model in the organization so that now you can have more control than just "Write"

🙇 thanks!

Hi @mike waites! Did you have a chance to create a milestone for the next release? And let me know if you need any help

FWIW I will be updating the documentation on the website. I will create sections for python docs that we can import and extend

I’ve not created milestones yet @Oleg Nenashev please feel free to do so, I’ve not given the release side of things too much thought yet so if you have something in mind then I’m all ears.

I don't think it needs much planning right now, it is rather inspirational

has renamed the channel from "python-wiremock" to "wiremock-python"

FTR WireMock Python 3.0 scope: https://github.com/wiremock/python-wiremock/milestone/1

wondering if someone might have some insight on this. Im working on this branch https://github.com/wiremock/python-wiremock/pull/59 when running the example test suite in the container two empty folders are created inside of the mounted volume example/mappings examples/__files/ are these some default directories created by the jar file or something ? 🤔 I can't see to trace them in the python code so wondering if this is something the server is doing itself.

hi there! I just created a PR to update the pypi build script to use

python3 -m build

instead of `setup.py`: https://github.com/wiremock/python-wiremock/pull/62. We are seeing problems when installing wiremock due to the setuptools requirement

Any idea when a new version with the latest on master (that is, the switch to dropping setuptools) will be published in pypi?

@mike waites For WireMock Python releases, you can also enable the Release Drafter for better rendering that we could later unify across the org

FTR https://github.com/wiremock/.github/blob/main/.github/release_drafter.yml

@mike waites I am around for the next 3 hrs if needed

Hi @mike waites! Just to follow-up on the documentation, I would suggest converting all docs to Markdown to align with other projects, and using the default MkDocs for now - https://docs.readthedocs.io/en/stable/intro/getting-started-with-mkdocs.html . I think it would be reasonable to keep the docs either on readthedocs, or inside the repository directly, and just reference them from wiremock.oeg

@mike waites Any ideas/preferences about the opengraph for WireMock Python? I could craft something like "WireMock ❤️ Python" or https://wiremock.org/docs/solutions/python/ but more original ideas are welcome

@mike waites just a small docs patch. You cleaned up almost everything already 🙂 https://github.com/wiremock/python-wiremock/pull/66

🎉 wiremock-python 2.4.0 GA release has been shipped 🎉 https://github.com/wiremock/python-wiremock/releases/tag/2.4.0

📢 We've got an approval from the Python Foundation for WireMock Python customized logo and artwork. I will add them, including SVGs, to the wiremock/community repository

Logos are here: https://github.com/wiremock/python-wiremock/pull/67

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?

👋 @mike waites How we are doing with the Testcontainers implementation? Any help needed? Asking for https://github.com/testcontainers/community-module-registry/pull/3