Repository navigation
Looking for co-maintainers #1434
Description
To remove the bus-factor a bit I am looking for co-maintainers. As mentioned in the README I don't foresee much new features to be developed, but mostly making sure it works with new Python versions and dependencies.
I am looking for co-maintainers with a bit of a proven trackrecord
Activity
ffrank commentedon Dec 26, 2024
I'm definitely tempted to try and bring some order to the backlog of PRs and issues, if that would be welcome.
bendikro commentedon Mar 17, 2025
@ffrank Could you maybe look at #1446 and make a new release?
ffrank commentedon Mar 18, 2025
I never got reply to my previous offer, and my focus has since shifted.
bendikro commentedon Mar 19, 2025
@mvantellingen If you want help with maintaining, you need to answer when people show up.
bfontaine commentedon May 6, 2025
I don’t know anything about SOAP but I can help with triaging PR and issues, if needed.
DylanMerigaud commentedon Oct 3, 2026
Hi Michael, I would like to help with this, on the part you describe: keeping zeep working with new Python versions and dependencies.
To start with something you can judge, I opened #1501 for #1417 (zeep ships the SOAP encoding schema instead of fetching it).
On #1486: the test suite of main passes unchanged on Python 3.15.0rc2 (macOS, without the xmlsec extra) with lxml 6.1.3 installed from its wheel. lxml 6.1.3 ships 3.15 wheels, but uv.lock still pins 6.1.1, which has none, so that issue looks like an lxml bump in the lock plus 3.15 in the CI matrix and classifiers.
If that is useful, I can go through the open PRs and list the ones that are small, tested and still apply on main, so the next release takes you less time.