suds-py3
suds-py3 copied to clipboard
cackharot
zeep
Hi! I'd been maintaining a suds fork for a few years (which fixed different bugs compared to this fork, but also had its own bugs too).
A few months back, I came across zeep. It's a true successor to suds, and the authors did a really good job on python3 support, and lots of bug-fixing and enhancements.
I ended up dropping my suds fork in favour of this since the quality and reliability is a lot higher, and have started reaching out to other suds maintainers and pointing them in that direction. I'd like to gradually try and help the "we have 10 forks each with different fixes" situation, and have a single standard tool used by the entire ecosystem.
I know that dumping one's own work is usually quite hard, but I'm wondering how you'd feel about pointing users to zeep in future, so that new and existing project can gradually move over.
I really hope you don't take this the wrong way, I'm aware that it's a controversial thing to propose.
Speaking as someone who has bounced between suds forks for the last few years I would love to see an official rally point everyone can contribute to. Excited to hear about zeep (trying it in a project now).
@WhyNotHugo I can understand the desire to have one repository with every one contributing to it, and zeep looks like it has a lot of activity in that area and quite a few issues (some issues like I have had do not have any answers). The benefit of suds-py is that it has been stable with few issues and simple. Zeep has more options, but with more options comes complexity and problems. It is nice having the simple interface of suds-py to work with.
I'm currently implementing a soap utility that hits a lot of different soap configurations and have been flipping back and forth between suds and zeep. I've had issues with both (more with zeep), but when suds works, its simplicity wins with sending requests and dealing with returns.
Speaking as someone who has bounced between suds forks for the last few years I would love to see an official rally point everyone can contribute to. Excited to hear about zeep (trying it in a project now).
how about moving all these projects into @jazzband to make sure there's a rallying point for continued maintainer-ship of all these forks?
Zeep is well maintained and has plenty of activity. If you'd like to direct your efforts towards one suds fork, I'd suggest you seriously consider it.
@WhyNotHugo I use suds via psphere, I'm not familiar with suds or soap and so would need help porting to zeep: see https://github.com/psphere-project/psphere/pull/28